dbcve.org
Openstack PlatformApplication · Redhat

CVE-2024-7319

MEDIUM · 5.0 CVSS v3.1 Published 2024-08-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/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
An incomplete fix for CVE-2023-1625 was found in openstack-heat. Sensitive information may possibly be disclosed through the OpenStack stack abandon command with the hidden feature set to True and the CVE-2023-1625 fix applied.

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 · moderate confidence

This is an incomplete fix for CVE-2023-1625 in OpenStack Heat. Even with the CVE-2023-1625 fix applied, sensitive information can still be disclosed through the OpenStack stack abandon command when the hidden feature is set to True. The original fix did not fully address the information disclosure vulnerability in the stack abandon functionality.

MitigationRestrict access to the stack abandon command and review who has permissions to use it until a complete patch is available. Monitor for any unauthorized stack abandon operations that may have exposed sensitive data.

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:= 13.0= 16.1= 16.2= 17.0
HeatApplication
Affected:all versions

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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. Identify OpenStack Heat deployment
    Determine if OpenStack Heat orchestration service is deployed in your environment. Check for Heat components in your OpenStack installation or list the installed OpenStack services.
    Affected if OpenStack Heat is not present in the environment, this CVE does not apply.
  2. Verify Heat service version
    Check the installed version of the OpenStack Heat service against the affected version ranges: Red Hat OpenStack Platform versions 13.0, 16.1, 16.2, 17.0, or any version of OpenStack Heat.
    Affected if The installed version falls within or matches the affected versions.
  3. Locate hidden parameter configuration
    Identify where the 'hidden' parameter or feature flag is configured for stack resources in your Heat templates or environment files. This is typically found in Heat environment files or resource definition templates.
    Affected if The 'hidden' parameter exists and is set to True in your Heat configuration.
  4. Check stack abandon permissions
    Determine which users or roles have permission to execute the stack abandon command in your OpenStack deployment. Review the policy.json or RBAC settings for the abandon action.
    Affected if Users other than restricted administrators can execute stack abandon.
  5. Audit recent stack abandon operations
    Review Heat service logs for any stack abandon operations that may have been performed, especially on stacks where the hidden parameter was set to True.
    Affected if Stack abandon operations have been performed on stacks with hidden=True.

You are affected if OpenStack Heat is deployed with the hidden parameter set to True and users with stack abandon permissions exist in your environment.

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 the stack abandon command and review who has permissions to use it until a complete patch is available. Monitor for any unauthorized stack abandon operations that may have exposed sensitive data.

Fix this in Openstack Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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