GHSA-pg64-r7rr-phv8 CVE-2019-14433 PYSEC-2019-191
OpenStack Nova Server Resource Faults Leak External Exception Details
Medium
PyPI
- Severity
- 0.0 / 10
- Medium · CVSS 4.0
- Exploit chance (EPSS)
- 1.94%
- Chance of exploitation in the next 30 days. Higher than 80.15% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- CWE-209 Generation of Error Message Containing Sensitive Information
- Fix
17.0.12- Upgrade nova to this version or later
Description
An issue was discovered in OpenStack Nova before 17.0.12, 18.x before 18.2.2, and 19.x before 19.0.2. If an API request from an authenticated user ends in a fault condition due to an external exception, details of the underlying environment may be leaked in the response, and could include sensitive configuration or other data.
Affected versions
PyPI
| Package | Vulnerable | Fixed in |
|---|---|---|
| nova | < 17.0.12 |
17.0.12 |
| nova | >= 18.0.0, < 18.2.2 |
18.2.2 |
| nova | >= 19.0.0, < 19.0.2 |
19.0.2 |
| nova | >= 19.0.0, < 19.0.2< 17.0.12>= 18.0.0, < 18.2.2 |
17.0.1218.2.219.0.2 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
nova PyPI → 17.0.12
- pip
pip install --upgrade "nova>=17.0.12"- poetry
poetry add "nova>=17.0.12"- uv
uv add "nova>=17.0.12"
Severity breakdown
CVSS 4.0 0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Attack vector
- Network
- Attack complexity
- Low
- Attack requirements
- None
- Privileges required
- Low
- User interaction
- None
- Confidentiality (vulnerable system)
- High
- Integrity (vulnerable system)
- None
- Availability (vulnerable system)
- None
- Confidentiality (subsequent systems)
- None
- Integrity (subsequent systems)
- None
- Availability (subsequent systems)
- None
CVSS 3.1 6.5
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Weakness
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
CWE-209: Generation of Error Message Containing Sensitive Information
The product generates an error message that includes sensitive information about its environment, users, or associated data.
How to prevent it
- Implementation: Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
- Implementation: Handle exceptions internally and do not display errors containing potentially sensitive information to a user.
- Implementation: Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
- Implementation, Build and Compilation: Debugging information should not make its way into a production release.
- Implementation, Build and Compilation: Debugging information should not make its way into a production release.
- System Configuration: Where available, configure the environment to use less verbose error messages. For example, in PHP, disable the display_errors setting during configuration, or at runtime using the error_reporting() function.
- System Configuration: Create default error pages or messages that do not leak any information.
References
Advisories
Packages
Other links
- github.com/openstack/nova/commit/298b337a16c0d10916b4431c436d19b3d6f5360e
- access.redhat.com/errata/RHSA-2019:2622
- access.redhat.com/errata/RHSA-2019:2631
- access.redhat.com/errata/RHSA-2019:2652
- github.com/pypa/advisory-database/tree/main/vulns/nova/PYSEC-2019-191.yaml
- launchpad.net/bugs/1837877
- lists.debian.org/debian-lts-announce/2022/09/msg00018.html
- security.openstack.org/ossa/OSSA-2019-003.html
- usn.ubuntu.com/4104-1
- openwall.com/lists/oss-security/2019/08/06/6
- usn.ubuntu.com/4104-1
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-mfg3-p6m3-gjgr OpenStack Nova: Nova scheduler hint injection bypasses Placement resource claims and scheduling constraints | High | Also affects nova |
| GHSA-m4f3-qp2w-gwh6 OpenStack Nova calls qemu-img without format restrictions for resize | High | Also affects nova |
| GHSA-rm86-h44c-2r2m OpenStack Nova vulnerable to unauthorized access to potentially sensitive data | Medium | Also affects nova |
| GHSA-r4v4-w9pv-6fph OpenStack Cinder, Glance, and Nova vulnerable to arbitrary file access | Medium | Also affects nova |
| GHSA-7h75-hwxx-qpgc OpenStack Cinder, glance, and Nova vulnerable to Path Traversal | Medium | Also affects nova |
| GHSA-v725-c588-h936 OpenStack Nova Changing vnic_type breaks compute service restart | Low | Also affects nova |
| GHSA-22jm-4hxw-35jf OpenStack Nova can leak consoleauth token into log files | Low | Also affects nova |
| GHSA-43cm-73px-5v4m OpenStack Compute (Nova) Resource limit circumvention in Nova private flavors | Low | Also affects nova |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor