# CVE-2024-12369: Elytron-oidc-client: oidc authorization code injection > Attackers can inject stolen authorization codes to hijack victim sessions in Red Hat JBoss EAP OIDC clients, leading to account takeover. - **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 9 Dec 2024 - **Updated:** 4 Aug 2026 - **Also known as:** GHSA-5565-3c98-g6jc ## What is CVE-2024-12369? CVE-2024-12369 is a medium-severity authentication bypass vulnerability in Red Hat Build of Keycloak, published on 9 Dec 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official 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. Weakness: CWE-345 (Insufficient Verification of Data Authenticity) ## Which versions are affected by CVE-2024-12369? 8 open source packages ship an affected version, including org.wildfly.security:wildfly-elytron and org.wildfly.security:wildfly-elytron-http-oidc. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.wildfly.security:wildfly-elytron` | Maven | From 1.17.0.Final | 2.2.9.Final | | `org.wildfly.security:wildfly-elytron` | Maven | From 1.17.0.Final | 2.2.9.Final | | `org.wildfly.security:wildfly-elytron` | Maven | From 2.3.0.Final | 2.6.2.Final | | `org.wildfly.security:wildfly-elytron` | Maven | From 2.3.0.Final | 2.6.2.Final | | `org.wildfly.security:wildfly-elytron-http-oidc` | Maven | From 1.17.0.Final | 2.2.9.Final | | `org.wildfly.security:wildfly-elytron-http-oidc` | Maven | From 1.17.0.Final | 2.2.9.Final | | `org.wildfly.security:wildfly-elytron-http-oidc` | Maven | From 2.3.0.Final | 2.6.2.Final | | `org.wildfly.security:wildfly-elytron-http-oidc` | Maven | From 2.3.0.Final | 2.6.2.Final | ## How do I fix CVE-2024-12369? Upgrade org.wildfly.security:wildfly-elytron to a fixed version for your release line: 2.2.9.Final or 2.6.2.Final. ## Is CVE-2024-12369 being exploited? There is no known exploitation of CVE-2024-12369 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-12369 and fix it if it is affected. What it is: CVE-2024-12369 is a medium-severity authentication bypass vulnerability in Red Hat Build of Keycloak, published on 9 Dec 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-12369 in the wild and no public exploit code. Affected packages and fixed versions: - org.wildfly.security:wildfly-elytron (Maven): affected from 1.17.0.Final; fixed in 2.2.9.Final - org.wildfly.security:wildfly-elytron (Maven): affected from 1.17.0.Final; fixed in 2.2.9.Final - org.wildfly.security:wildfly-elytron (Maven): affected from 2.3.0.Final; fixed in 2.6.2.Final - org.wildfly.security:wildfly-elytron (Maven): affected from 2.3.0.Final; fixed in 2.6.2.Final - org.wildfly.security:wildfly-elytron-http-oidc (Maven): affected from 1.17.0.Final; fixed in 2.2.9.Final - org.wildfly.security:wildfly-elytron-http-oidc (Maven): affected from 1.17.0.Final; fixed in 2.2.9.Final - org.wildfly.security:wildfly-elytron-http-oidc (Maven): affected from 2.3.0.Final; fixed in 2.6.2.Final - org.wildfly.security:wildfly-elytron-http-oidc (Maven): affected from 2.3.0.Final; fixed in 2.6.2.Final Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-12369/ (Markdown: https://insights.sbomify.com/CVE-2024-12369/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-12369 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-12369 - OSV: https://osv.dev/vulnerability/CVE-2024-12369 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-12369/ Summaries are generated and may contain mistakes; the official description above is the record.