CVE-2024-7557VulnerabilityPublished 8 Aug 2024Updated 19 Mar 2026

CVE-2024-7557: odh-dashboard · Authentication Bypass by Primary Weakness

Affects odh-dashboardSource CVE Database V5

Not known to be exploited · CVSS 8.8 High : upgrade to 2.9.0 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

8.8High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.9.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade opendatahub-io/odh-dashboard to 2.9.0.

Affected software

Product	Affected	Fixed in
GitHubopendatahub-io/odh-dashboard`pkg:github/opendatahub-io/odh-dashboard`Other threats	Affected >=2.8.0 <2.9.0 =2.11	Fixed in 2.9.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately audit and restrict access to the OpenShift AI UI to trusted administrators only to reduce token exposure. 2. Implement strict Role-Based Access Control (RBAC) policies to limit ServiceAccount permissions to the minimum necessary scope, preventing excessive privileges. 3. Enforce namespace isolation best practices to ensure that tokens and credentials are not shared or accessible across models or projects. 4. Monitor and rotate ServiceAccount tokens regularly to reduce the window of opportunity for token reuse attacks. 5. Use network policies to restrict access to APIs and services within namespaces, limiting the attack surface. 6. 7. Employ runtime security tools to detect anomalous use of oc CLI commands or token misuse. 8. Educate developers and administrators about the risks of token exposure in UI components and encourage secure deployment practices. 9. Consider deploying additional authentication layers or token encryption mechanisms if supported by the platform. 10. Conduct regular security assessments and penetration testing focused on authentication and privilege escalation vectors within OpenShift environments.

Description

A vulnerability was found in OpenShift AI that allows for authentication bypass and privilege escalation across models within the same namespace. When deploying AI models, the UI provides the option to protect models with authentication. However, credentials from one model can be used to access other models and APIs within the same namespace. The exposed ServiceAccount tokens, visible in the UI, can be utilized with oc --token={token} to exploit the elevated view privileges associated with the ServiceAccount, leading to unauthorized access to additional resources.

Impact

The vulnerability allows attackers to bypass authentication controls and escalate privileges within OpenShift AI namespaces, potentially compromising all AI models and APIs deployed therein. This can lead to unauthorized data access, modification, or deletion, impacting confidentiality, integrity, and availability of AI workloads. Organizations relying on OpenShift AI for critical AI model deployment and inference may face data breaches, intellectual property theft, or service disruption. The ability to reuse tokens across models breaks the security boundary between tenants or projects, increasing the risk of lateral movement and broader compromise within containerized environments. Given OpenShift's widespread use in enterprise and cloud-native deployments, this vulnerability could affect organizations in sectors such as finance, healthcare, technology, and government, where AI workloads are sensitive. The lack of required user interaction and the low complexity of exploitation increase the likelihood of targeted attacks once exploit code becomes available. The absence of known exploits currently provides a window for remediation but also underscores the urgency to patch and harden affected systems.

References

Community reviews

Loading reviews…