GHSA-vcmv-6rxx-fh7r CVE-2011-4076 PYSEC-2026-691
OpenStack Nova Exposure of Sensitive Information to an Unauthorized Actor
- Severity
- 5.9 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 1.46%
- Chance of exploitation in the next 30 days. Higher than 73.54% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Fix
12.0.0a0- Upgrade nova to this version or later
Description
OpenStack Nova before 2012.1 allows someone with access to an EC2_ACCESS_KEY (equivalent to a username) to obtain the EC2_SECRET_KEY (equivalent to a password). Exposing the EC2_ACCESS_KEY via http or tools that allow man-in-the-middle over https could allow an attacker to easily obtain the EC2_SECRET_KEY. An attacker could also presumably brute force values for EC2_ACCESS_KEY.
Affected versions
PyPI
| Package | Vulnerable | Fixed in |
|---|---|---|
| nova | < 12.0.0a0 |
12.0.0a0 |
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 → 12.0.0a0
- pip
pip install --upgrade "nova>=12.0.0a0"- poetry
poetry add "nova>=12.0.0a0"- uv
uv add "nova>=12.0.0a0"
Severity breakdown
CVSS 3.1 5.9
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- 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.
References
Advisories
Packages
Other links
- github.com/openstack/nova/commit/b1ab6da1495784ff581000018a6047fd19cf82c4
- github.com/openstack/nova/commit/beee11edbfdd82cd81bc9c0fd75912c167892c2b
- access.redhat.com/security/cve/cve-2011-4076
- bugs.launchpad.net/nova/+bug/868360
- bugzilla.redhat.com/show_bug.cgi
- security-tracker.debian.org/tracker/CVE-2011-4076
- openwall.com/lists/oss-security/2011/10/25/4
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