CVE-2024-12369 is a medium-severity (CVSS 4.2) CWE-345 vulnerability in org.wildfly.security:wildfly-elytron. O3 Security confirms whether CVE-2024-12369 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Elytron-oidc-client: oidc authorization code injection
Real-World Exposure
org.wildfly.security:wildfly-elytron☕org.wildfly.security:wildfly-elytron☕org.wildfly.security:wildfly-elytron-http-oidc☕org.wildfly.security:wildfly-elytron-http-oidcReal-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 vulnerability was found in OIDC-Client. When using the RH SSO OIDC adapter with EAP 7.x or when using the elytron-oidc-client subsystem with EAP 8.x, authorization code injection attacks can occur, allowing an attacker to inject a stolen authorization code into the attacker's own session with the client with a victim's identity. This is usually done with a Man-in-the-Middle (MitM) or phishing attack.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.wildfly.security:wildfly-elytron | ≥ 1.17.0.Final&&< 2.2.9.Final | 2.2.9.Final |
| ☕Maven | org.wildfly.security:wildfly-elytron | ≥ 2.3.0.Final&&< 2.6.2.Final | 2.6.2.Final |
| ☕Maven | org.wildfly.security:wildfly-elytron-http-oidc | ≥ 1.17.0.Final&&< 2.2.9.Final | 2.2.9.Final |
| ☕Maven | org.wildfly.security:wildfly-elytron-http-oidc | ≥ 2.3.0.Final&&< 2.6.2.Final | 2.6.2.Final |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wildfly.security:wildfly-elytron. 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.
Fix
Update org.wildfly.security:wildfly-elytron to 2.2.9.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-12369 is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 pinpoints whether CVE-2024-12369 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 CVE-2024-12369. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-12369 in your dependencies?
O3 detects CVE-2024-12369 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.