Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-12369: Insufficient Verification of Data Authenticity

0
Medium
VulnerabilityCVE-2024-12369cvecve-2024-12369
Published: Mon Dec 09 2024 (12/09/2024, 20:53:09 UTC)
Source: CVE Database V5

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/28/2026, 11:44:21 UTC

Technical Analysis

CVE-2024-12369 is a vulnerability identified in the OIDC-Client implementation within Red Hat Single Sign-On (RH SSO) adapters for EAP 7.x and the elytron-oidc-client subsystem in EAP 8.x. The vulnerability arises from insufficient verification of data authenticity during the authorization code exchange process in the OpenID Connect (OIDC) protocol. Specifically, an attacker can inject a stolen authorization code into their own session with the client, effectively impersonating the victim's identity. This attack vector typically requires the attacker to intercept or phish the authorization code, often through Man-in-the-Middle (MitM) attacks or social engineering techniques. Once the attacker injects the stolen code, they can gain unauthorized access to resources or services under the victim's identity. The vulnerability affects confidentiality and integrity of user sessions but does not impact system availability. The CVSS v3.1 base score is 4.2, indicating medium severity, with attack vector being network-based, requiring high attack complexity, no privileges, and user interaction. No patches or known exploits are currently publicly available, but the risk remains significant for organizations relying on these specific OIDC client implementations in Red Hat EAP environments.

Potential Impact

The primary impact of CVE-2024-12369 is unauthorized identity impersonation, which can lead to unauthorized access to sensitive resources and data within affected organizations. Attackers exploiting this vulnerability can bypass authentication controls by injecting stolen authorization codes, potentially gaining access to user accounts and associated privileges. This undermines the confidentiality and integrity of user sessions and data. While availability is not directly affected, the breach of identity can facilitate further attacks such as data exfiltration, privilege escalation, or lateral movement within networks. Organizations relying on RH SSO OIDC adapters or elytron-oidc-client subsystems in EAP 7.x and 8.x are at risk, particularly those with high-value or sensitive applications integrated with these authentication mechanisms. The requirement for MitM or phishing attacks means that environments with weak network security or user awareness are more vulnerable. The medium CVSS score reflects the moderate ease of exploitation combined with significant potential impact on identity security.

Mitigation Recommendations

To mitigate CVE-2024-12369, organizations should first verify if they are using the affected versions of RH SSO OIDC adapters with EAP 7.x or elytron-oidc-client subsystem with EAP 8.x. Immediate steps include: 1) Applying any available patches or updates from Red Hat as soon as they are released. 2) Implementing network-level protections such as enforcing TLS with strong cipher suites to prevent MitM attacks. 3) Enhancing phishing detection and user training to reduce the risk of social engineering attacks that could expose authorization codes. 4) Employing additional OIDC security best practices such as using Proof Key for Code Exchange (PKCE) to bind authorization codes to client sessions, if supported. 5) Monitoring authentication logs for unusual authorization code usage or session anomalies that may indicate exploitation attempts. 6) Restricting the lifespan and scope of authorization codes to minimize the window of opportunity for attackers. 7) Considering multi-factor authentication (MFA) to add an additional layer of identity verification beyond the authorization code. These measures collectively reduce the risk of successful exploitation and limit potential damage.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
redhat
Date Reserved
2024-12-09T16:33:36.277Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68e0f3c0b66c7f7acdd3d07e

Added to database: 10/4/2025, 10:15:28 AM

Last enriched: 2/28/2026, 11:44:21 AM

Last updated: 3/25/2026, 4:06:30 AM

Views: 59

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses