VulnerabilityPublished 24 Jul 2024Updated 20 Nov 2025

CVE-2024-7079: openshift-console · Missing Authentication

Affects openshift-consoleSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

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

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: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jul 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 26 Oct 2026.

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

Affected software

Product	Affected	Fixed in
Red Hatredhat/openshift-console`pkg:rpm/redhat/openshift-console`Other threats	Affected =4.16	Fixed in–

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

AI-suggested

To mitigate CVE-2024-7079, organizations should immediately verify if their OpenShift console version is 4.16 and restrict access to the /API/helm/verify endpoint. Applying any available patches or updates from Red Hat that address this authentication flaw is the most effective measure. In the absence of an official patch, administrators should implement network-level access controls such as firewall rules or API gateway policies to restrict access to the vulnerable endpoint only to trusted users or internal networks. Additionally, auditing and monitoring access logs for unusual or unauthorized requests to this endpoint can help detect exploitation attempts. Reviewing and strengthening authentication middleware logic to ensure proper credential validation before granting access to critical API functions is essential. Organizations should also consider isolating the OpenShift console from public networks or enforcing VPN access to reduce exposure. Finally, educating DevOps and security teams about this vulnerability will help ensure rapid response and remediation.

Description

A flaw was found in the Openshift console. The /API/helm/verify endpoint is tasked to fetch and verify the installation of a Helm chart from a URI that is remote HTTP/HTTPS or local. Access to this endpoint is gated by the authHandlerWithUser() middleware function. Contrary to its name, this middleware function does not verify the validity of the user's credentials. As a result, unauthenticated users can access this endpoint.

Impact

The primary impact of CVE-2024-7079 is unauthorized access to the /API/helm/verify endpoint, which can lead to exposure of internal Helm chart verification processes. While this does not directly compromise system integrity or availability, it poses a confidentiality risk by allowing attackers to gather information about Helm chart installations and configurations. This information could be leveraged to craft targeted attacks, such as deploying malicious Helm charts or exploiting other vulnerabilities in the deployment pipeline. For organizations relying heavily on OpenShift for container orchestration and Helm for package management, this vulnerability could facilitate reconnaissance activities by unauthenticated attackers, increasing the risk of subsequent exploitation. The medium severity rating reflects the limited scope of impact but acknowledges the critical nature of the function exposed. Since no authentication is enforced, the attack surface is broad, potentially allowing remote attackers to exploit this flaw without any credentials or user interaction. This could be particularly impactful in environments where OpenShift consoles are exposed to untrusted networks or the internet.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 03:52 UTC

Technical details

References

Community reviews

Related threats