Skip to content

GHSA-g2j5-7vgx-6xrx CVE-2015-5162 PYSEC-2026-2412 PYSEC-2026-2491 PYSEC-2026-871

OpenStack Cinder, Glance, and Nova contain Uncontrolled Resource Consumption

High PyPI
Severity
7.5 / 10
High · CVSS 3.0
Exploit chance (EPSS)
3.09%
Chance of exploitation in the next 30 days. Higher than 87.71% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-400 Uncontrolled Resource Consumption
Fix
Available
3 packages have a fixed version

Description

The image parser in OpenStack Cinder prior to 7.0.2, and 8.0.0 and above, prior to 9.0.0; Glance prior to 14.00; and Nova prior to 12.0.4 does not properly limit qemu-img calls, which might allow attackers to cause a denial of service (memory and disk consumption) via a crafted disk image. This issue is patched in Cinder 7.0.2 and 9.0.0; Glance 14.0.0; and Nova 12.0.4

Affected versions

PyPI

PackageVulnerableFixed in
cinder
< 7.0.2
7.0.2
cinder
>= 8.0.0, < 9.0.0
9.0.0
cinder
< 7.0.2
>= 8.0.0, < 9.0.0
7.0.2
9.0.0
glance
< 14.0.0
14.0.0
nova
< 12.0.4
12.0.4

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.

cinder PyPI → 7.0.2

pip
pip install --upgrade "cinder>=7.0.2"
poetry
poetry add "cinder>=7.0.2"
uv
uv add "cinder>=7.0.2"

glance PyPI → 14.0.0

pip
pip install --upgrade "glance>=14.0.0"
poetry
poetry add "glance>=14.0.0"
uv
uv add "glance>=14.0.0"

nova PyPI → 12.0.4

pip
pip install --upgrade "nova>=12.0.4"
poetry
poetry add "nova>=12.0.4"
uv
uv add "nova>=12.0.4"

Severity breakdown

CVSS 3.0 7.5

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

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Weakness

CWE-400: Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource.

How to prevent it
  • Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
  • Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
  • Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
  • Implementation: Ensure that all failures in resource allocation place the system into a safe posture.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy 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 cinder
GHSA-7h75-hwxx-qpgc
OpenStack Cinder, glance, and Nova vulnerable to Path Traversal
Medium Also affects cinder
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
Is this in your code?

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