dbcve.org
Openstack PlatformApplication · Redhat

CVE-2024-8007

HIGH · 8.1 CVSS v3.1 Published 2024-08-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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 openstack-tripleo-common component of the Red Hat OpenStack Platform (RHOSP) director. This vulnerability allows an attacker to deploy potentially compromised container images via disabling TLS certificate verification for registry mirrors, which could enable a man-in-the-middle (MITM) attack.

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

A flaw in the openstack-tripleo-common component of Red Hat OpenStack Platform director allows TLS certificate verification to be disabled for container registry mirrors. This permits man-in-the-middle attacks and enables deployment of potentially compromised container images.

MitigationEnsure TLS certificate verification is enforced for all registry mirrors in the OpenStack director configuration and verify that no configuration options exist that allow disabling TLS verification.

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
Openstack PlatformApplication
Affected:= 16.1= 16.2= 17.1

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify openstack-tripleo-common package version
    Run 'rpm -q openstack-tripleo-common' or check the installed version via 'pip show tripleo-common' if installed via pip. Compare the version against the affected Red Hat OpenStack Platform versions 16.1, 16.2, and 17.1.
    Affected if The openstack-tripleo-common package is installed as part of Red Hat OpenStack Platform versions 16.1, 16.2, or 17.1.
  2. Locate container registry mirror configuration
    Search for configuration files under /var/lib/tripleo-config/, /home/stack/, or the director deployment directory for entries containing 'registry', 'mirror', or 'insecure' settings. Common locations include container-image-prepare.yaml, containers-prepare.yaml, or undercloud.conf in the director deployment.
    Affected if Configuration files exist that define container registry mirrors for the OpenStack director.
  3. Inspect registry mirror settings for TLS verification
    Examine the found registry configuration files and look for any parameters that control TLS certificate verification, such as 'insecure', 'insecure_registry', 'tls_verify', 'verify_tls', or similar options. Check both undercloud and overcloud related configurations.
    Affected if Any registry mirror configuration contains a setting that disables or can disable TLS certificate verification (e.g., insecure=true, tls_verify=false).
  4. Check environment templates for disable flags
    Review tripleo-heat-templates and any custom environment YAML files in the deployment for container registry related parameters. Look specifically for flags that control TLS verification behavior on registry connections.
    Affected if Environment templates contain parameters that explicitly disable TLS verification for container registries.

A system is affected if it runs Red Hat OpenStack Platform 16.1, 16.2, or 17.1 with openstack-tripleo-common and has any container registry mirror configuration that disables or allows disabling TLS certificate verification.

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

Ensure TLS certificate verification is enforced for all registry mirrors in the OpenStack director configuration and verify that no configuration options exist that allow disabling TLS verification.

Fix this in Openstack Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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