dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-1139

HIGH · 7.7 CVSS v3.1 Published 2024-04-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
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 credentials leak vulnerability was found in the cluster monitoring operator in OCP. This issue may allow a remote attacker who has basic login credentials to check the pod manifest to discover a repository pull secret.

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 cluster monitoring operator in OpenShift Container Platform exposes repository pull credentials through pod manifests that are readable by users with basic login privileges. An authenticated attacker with minimal access can view pod manifests to extract stored repository pull secrets.

MitigationRestrict access to pod manifests in the cluster monitoring operator namespace or rotate the exposed pull secrets and reconfigure the operator to use a more secure secret management approach.

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

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
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Confirm OpenShift Container Platform is deployed
    Check if the cluster is running OpenShift by running 'oc get clusterversion' or checking for the 'openshift' namespace
    Affected if The cluster is running OpenShift Container Platform and has the cluster monitoring operator installed
  2. Identify the cluster monitoring operator namespace
    Run 'oc get namespaces | grep -E "monitoring|openshift-monitoring"' to find the monitoring namespace, typically 'openshift-monitoring'
    Affected if The cluster monitoring operator is deployed in a namespace accessible to basic users
  3. Check if basic users can read pod manifests in the monitoring namespace
    Run 'oc auth can-i get pods --as=<regular-user>' in the openshift-monitoring namespace, or attempt to list pods as a non-privileged user with 'oc get pods -n openshift-monitoring --as=<test-user>'
    Affected if Users with basic login privileges (cluster-reader role or similar) can list and view pods in the monitoring namespace
  4. Inspect pod manifests for exposed pull secrets
    Run 'oc get pods -n openshift-monitoring -o yaml' and search for 'imagePullSecrets' or 'pull_secret' fields in the pod specifications, or check specific operator pods like 'prometheus-k8s-*'
    Affected if Pod manifests in the monitoring namespace contain 'imagePullSecrets' or references to repository pull credentials
  5. Verify secret access by basic users
    Run 'oc get secrets -n openshift-monitoring --as=<test-user>' to check if non-admin users can read secret resources, or check if secrets are mounted as volumes in pod definitions
    Affected if Repository pull secrets (e.g., registry credentials) are accessible or visible to users with basic cluster access

A user is affected if OpenShift Container Platform with cluster monitoring operator is deployed AND users with basic login privileges can view pod manifests or secrets containing repository pull credentials in the monitoring namespace.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access to pod manifests in the cluster monitoring operator namespace or rotate the exposed pull secrets and reconfigure the operator to use a more secure secret management approach.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1139 — 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-1139 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