dbcve.org
Openstack PlatformApplication · Redhat

CVE-2022-3596

HIGH · 7.5 CVSS v3.1 Published 2023-09-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
An information leak was found in OpenStack's undercloud. This flaw allows unauthenticated, remote attackers to inspect sensitive data after discovering the IP address of the undercloud, possibly leading to compromising private information, including administrator access credentials.

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

An information disclosure vulnerability in OpenStack's undercloud component allows unauthenticated remote attackers to access sensitive data, including administrator credentials, simply by discovering the undercloud's IP address. The flaw stems from improper access controls on the undercloud service.

MitigationRestrict network access to the undercloud interface (e.g., via firewall rules or network segmentation), implement proper authentication requirements, and immediately rotate any credentials that may have been exposed.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify OpenStack Platform version
    Run 'openstack version show' or check /etc/rhosp-version or the Red Hat OpenStack Platform subscription management to confirm the installed version is 13.0
    Affected if The installed version is Red Hat OpenStack Platform 13.0 (exact match)
  2. Locate undercloud IP address
    Check the undercloud's public or management IP address by reviewing the undercloud configuration (typically in /home/stack/undercloud.conf or via 'openstack endpoint list' and 'openstack service list' output)
    Affected if An undercloud IP address exists and is reachable on the network
  3. Verify undercloud network exposure
    Attempt to access common undercloud service ports (e.g., HTTP on 80/8080, HTTPS on 443, or the Horizon dashboard port) from an untrusted network interface, or review firewall rules and network configuration to determine if the undercloud is accessible without authentication
    Affected if The undercloud service is accessible from networks that should not have access (e.g., directly from the internet or untrusted subnets)
  4. Confirm access control configuration
    Review the undercloud's HTTP service configuration and authentication settings - check whether the undercloud endpoints require authentication or if anonymous/unauthenticated access is permitted for sensitive endpoints
    Affected if Unauthenticated access to undercloud services is allowed or authentication enforcement is missing for sensitive endpoints that should expose admin credentials
  5. Check for credential exposure
    Review any accessible undercloud responses for presence of administrator credentials, tokens, or sensitive configuration data that should not be returned to unauthenticated users
    Affected if Sensitive data including admin credentials or tokens is returned without requiring authentication

If the environment runs Red Hat OpenStack Platform 13.0 and the undercloud interface is network-accessible without proper authentication enforcement, the environment is affected by this CVE.

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 network access to the undercloud interface (e.g., via firewall rules or network segmentation), implement proper authentication requirements, and immediately rotate any credentials that may have been exposed.

Fix this in Openstack Platform Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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