Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-v4mm-q8fv-r2w5

HIGHFix: wildfly/wildfly#17812

GHSA-v4mm-q8fv-r2w5 is a high-severity (CVSS 7.3) Server-Side Request Forgery (SSRF) vulnerability in org.wildfly.security:wildfly-elytron-realm-token. O3 Security confirms whether GHSA-v4mm-q8fv-r2w5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

WildFly Elytron: SSRF security issue

Also known asCVE-2024-1233
Published
Apr 9, 2024
Updated
May 4, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed

Real-World Exposure

1 pkg affected
org.wildfly.security:wildfly-elytron-realm-token

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A flaw was found in JwtValidator.resolvePublicKey in JBoss EAP, where the validator checks jku and sends a HTTP request. During this process, no whitelisting or other filtering behavior is performed on the destination URL address, which may result in a server-side request forgery (SSRF) vulnerability.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
Mavenorg.wildfly.security:wildfly-elytron-realm-tokenall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wildfly.security:wildfly-elytron-realm-token. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of org.wildfly.security:wildfly-elytron-realm-token has shipped for GHSA-v4mm-q8fv-r2w5 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-v4mm-q8fv-r2w5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-v4mm-q8fv-r2w5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A flaw was found in` JwtValidator.resolvePublicKey` in JBoss EAP, where the validator checks jku and sends a HTTP request. During this process, no whitelisting or other filtering behavior is performed on the destination URL address, which may result in a server-side request forgery (SSRF) vulnerability.
O3 Security · Impact-Aware SCA

Is GHSA-v4mm-q8fv-r2w5 in your dependencies?

O3 detects GHSA-v4mm-q8fv-r2w5 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.