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

CVE-2024-12369

MEDIUM

WildFly Elytron OpenID Connect Client ExtensionOIDC authorization code injection attack

Also known asGHSA-5565-3c98-g6jc
Published
Dec 9, 2024
Updated
Apr 12, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk15th percentile+0.12%
0.00%0.27%0.54%0.81%0.1%0.2%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected
☕org.wildfly.security:wildfly-elytron☕org.wildfly.security:wildfly-elytron☕org.wildfly.security:wildfly-elytron-http-oidc☕org.wildfly.security:wildfly-elytron-http-oidc

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 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

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.wildfly.security:wildfly-elytron≥ 1.17.0.Final&&< 2.2.9.Final2.2.9.Final
☕Mavenorg.wildfly.security:wildfly-elytron≥ 2.3.0.Final&&< 2.6.2.Final2.6.2.Final
☕Mavenorg.wildfly.security:wildfly-elytron-http-oidc≥ 1.17.0.Final&&< 2.2.9.Final2.2.9.Final
☕Mavenorg.wildfly.security:wildfly-elytron-http-oidc≥ 2.3.0.Final&&< 2.6.2.Final2.6.2.Final

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. 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. 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.

  3. 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.

  4. 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

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.
O3 Security · Impact-Aware SCA

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.

Scan my dependencies How O3 SCA works