OpenStack Compute (Nova) vulnerable to denial of service via XML Entity Expansion attack
The security group extension in OpenStack Compute (Nova) Grizzly 2013.1.3, Havana before havana-3, and earlier allows remote attackers to cause a denial of service (resource consumption and crash) via an XML Entity Expansion (XEE) attack. NOTE: this issue is due to an incomplete fix for CVE-2013-1664.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Python (PyPI) | nova | < 2013.2 | 2013.2 |
References
- https://nvd.nist.gov/vuln/detail/CVE-2013-4179
- https://access.redhat.com/errata/RHSA-2013:1199
- https://access.redhat.com/security/cve/CVE-2013-4179
- https://bugs.launchpad.net/ossa/+bug/1190229
- https://bugzilla.redhat.com/show_bug.cgi?id=989707
- https://opendev.org/openstack/nova
- http://rhn.redhat.com/errata/RHSA-2013-1199.html
- http://www.ubuntu.com/usn/USN-2005-1
- https://pypi.org/project/nova
- https://github.com/advisories/GHSA-j6xh-q826-55jw
- Weakness (CWE)
CWE-119- Platform
- Python (PyPI)
- Package
nova- Disclosed
- 17.05.2022
- Updated
- 11.10.2026 15:17
Sources and licenses
OSV / GitHub Advisory Database - PYSEC-2026-875 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-j6xh-q826-55jw - CC BY 4.0
Vulnerability history: nova
All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 49
- First → latest
- 08.2012 06.2026
- Without a fix
- 5
- Exploited in attacks
- 0
Severity breakdown
- Critical 1
- High 11
- Medium 29
- Low 8
Disclosures per year
- 2017: 1
- 2018: 0
- 2019: 1
- 2020: 1
- 2021: 0
- 2022: 34
- 2023: 1
- 2024: 2
- 2025: 0
- 2026: 2
earlier: 7
-
OpenStack Compute (Nova) vulnerable to denial of service via XML Entity Expansion attack this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.