dbcve.org
Openshift Container PlatformApplication · Redhat

CVE-2024-7079

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The OpenShift console's /api/helm/verify endpoint, which fetches and verifies Helm charts from remote HTTP/HTTPS or local sources, is protected by the authHandlerWithUser() middleware. However, this middleware fails to validate user credentials despite its name, allowing unauthenticated attackers to access a sensitive endpoint that can retrieve and verify arbitrary Helm chart content.

MitigationFix the authHandlerWithUser() middleware to properly validate user credentials before granting access to the /api/helm/verify endpoint, ensuring unauthenticated requests are rejected.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openshift Container PlatformApplication
Affected:= 3.11= 4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check OpenShift Container Platform version
    Run 'oc version' or check the cluster version with 'oc get clusterversion -o jsonpath='{.items[].status.desired.version}''
    Affected if The version is 3.11 or 4.0 (exact match)
  2. Verify the helm API is enabled
    Check if the Helm API resources exist in the cluster: 'oc get apiservices | grep helm' or attempt to list helm releases with 'oc get helmchartreleases -A'
    Affected if The Helm API is present and accessible in the cluster
  3. Test unauthenticated access to /api/helm/verify
    Send an unauthenticated HTTP request to the /api/helm/verify endpoint (e.g., curl -k https://<console-host>/api/helm/verify) without providing any authentication tokens
    Affected if The request returns a successful HTTP response rather than a 401/403 authentication error, indicating the endpoint accepts unauthenticated requests

A user is affected if they run OpenShift Container Platform version 3.11 or 4.0 and the /api/helm/verify endpoint accepts requests without requiring valid authentication credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Fix the authHandlerWithUser() middleware to properly validate user credentials before granting access to the /api/helm/verify endpoint, ensuring unauthenticated requests are rejected.

Recommended fix Moderate confidence

OpenShift Container Platform 4.14 or later (consult Red Hat lifecycle for current supported versions)

  1. Upgrade to a currently supported version of OpenShift Container Platform (RHOCP). OpenShift 3.11 reached end of life in June 2022 and OpenShift 4.0-4.3 reached end of life in November 2020.
  2. Consult the Red Hat OpenShift Container Platform lifecycle documentation to identify the appropriate target version for your deployment.
  3. Plan and execute an upgrade path from OpenShift 3.11 or 4.0 to a supported release (such as 4.14 or 4.15 as of late 2024).
  4. After upgrading, verify that the /API/helm/verify endpoint now requires proper authentication.
Caveat Upgrades from OCP 3.11 to 4.x require a migration process rather than in-place upgrade; ensure compatibility of applications and operators with the target 4.x version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openshift Container Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7079 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-7079 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data