How severe is GHSA-m454-cm7h-rqhh?

No CVSS score has been assigned to GHSA-m454-cm7h-rqhh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m454-cm7h-rqhh?

GHSA-m454-cm7h-rqhh affects the following packages: nova (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-m454-cm7h-rqhh?

Update nova to 12.0.0a0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m454-cm7h-rqhh is resolved across your whole dependency graph.

How do I detect GHSA-m454-cm7h-rqhh in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nova. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-m454-cm7h-rqhh if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-m454-cm7h-rqhh?

O3 pinpoints whether GHSA-m454-cm7h-rqhh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-m454-cm7h-rqhh actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-m454-cm7h-rqhh, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is GHSA-m454-cm7h-rqhh?

GHSA-m454-cm7h-rqhh is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-m454-cm7h-rqhh published, and has it been updated?

GHSA-m454-cm7h-rqhh was published on May 17, 2022 and was last updated on November 22, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-m454-cm7h-rqhh

GHSA-m454-cm7h-rqhh is a Path Traversal vulnerability in nova. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-m454-cm7h-rqhh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenStack Nova Directory traversal vulnerability

Also known asCVE-2012-3360

Published

May 17, 2022

Updated

Nov 22, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Blast Radius

1 pkg affected

🐍nova

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Directory traversal vulnerability in virt/disk/api.py in OpenStack Compute (Nova) Folsom (2012.2) and Essex (2012.1), when used over libvirt-based hypervisors, allows remote authenticated users to write arbitrary files to the disk image via a .. (dot dot) in the path attribute of a file element.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`nova`	all versions	12.0.0a0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Directory traversal vulnerability in virt/disk/api.py in OpenStack Compu…

github.comNVDAug 2012

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nova. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update nova to 12.0.0a0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m454-cm7h-rqhh is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-m454-cm7h-rqhh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-m454-cm7h-rqhh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Directory traversal vulnerability in `virt/disk/api.py` in OpenStack Compute (Nova) Folsom (2012.2) and Essex (2012.1), when used over libvirt-based hypervisors, allows remote authenticated users to write arbitrary files to the disk image via a .. (dot dot) in the path attribute of a file element.

O3 Security · Impact-Aware SCA

Is GHSA-m454-cm7h-rqhh in your dependencies?

O3 detects GHSA-m454-cm7h-rqhh across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works