CVE-2012-3447: OpenStack Compute (Nova) Arbitrary File Overwrite Vulnerability
Summary
CVE-2012-3447: virt/disk/api.py in OpenStack Compute (Nova) 2012.1.x before 2012.1.2 and Folsom before Folsom-3 allows remote authenticated users to overwrite arbitrary files via a symlink attack on a file in an image that uses a symli... Affects nova across 2 version ranges.
< ce4b2e27be45a85b310237615c47eb53f37bb5f3
< d9577ce9f266166a297488445b5b0c93c1ddb368
Fixed in ce4b2e27be45a85b310237615c47eb53f37bb5f3. How to fix ↓
Also tracked for
- nova · Debian:11
The same CVE-2012-3447 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
OpenStack Compute, also known as Nova, is an open-source cloud computing software platform that allows users to control large pools of compute, storage, and networking resources. It provides a scalable and flexible infrastructure for building and managing public and private clouds. Nova is written in Python and is widely used in various cloud deployments.
This vulnerability affects versions 2012.1.x before 2012.1.2 and Folsom before Folsom-3. It allows remote authenticated users to overwrite arbitrary files by exploiting a symlink attack on a file in an image that uses a symlink only readable by root. This vulnerability is a result of an incomplete fix for CVE-2012-3361.
Vulnerability Detail
The vulnerability in OpenStack Compute (Nova) allows remote authenticated users to overwrite arbitrary files. By exploiting a symlink attack on a file in an image that uses a symlink only readable by root, an attacker can manipulate the symlink to overwrite files that should not be accessible to them. This can lead to unauthorized modification or destruction of critical system files, potentially causing a denial of service or unauthorized access to sensitive information.
This vulnerability was introduced in version 0 of Nova and was fixed in commits ce4b2e27be45a85b310237615c47eb53f37bb5f3 and d9577ce9f266166a297488445b5b0c93c1ddb368.
How To Fix
Latest published version: 34.0.0 as of 22 Oct 2026
pip install --upgrade "nova==34.0.0"Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
ce4b2e27be45a85b310237615c47eb53f37bb5f3
This is the first release that contains the fix.
pip install --upgrade "nova==ce4b2e27be45a85b310237615c47eb53f37bb5f3"Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. It is recommended to apply the fix by updating to the latest version of OpenStack Compute (Nova).
Conclusion
The OpenStack Compute (Nova) Arbitrary File Overwrite vulnerability allows remote authenticated users to overwrite arbitrary files. It is important to update to the fixed version of Nova to mitigate the risk of unauthorized modification or destruction of critical system files. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for nova →
FAQ
OpenStack Compute, also known as Nova, is an open-source cloud computing software platform that provides scalable and flexible infrastructure for building and managing public and private clouds.
A symlink attack, also known as a symbolic link attack, is a type of security vulnerability where an attacker exploits the use of symbolic links to gain unauthorized access or manipulate files and directories.
This vulnerability allows remote authenticated users to overwrite arbitrary files, potentially leading to unauthorized modification or destruction of critical system files. It can result in a denial of service or unauthorized access to sensitive information.
To fix this vulnerability, it is recommended to update to OpenStack Compute (Nova) version 2012.1.2 or Folsom-3. Users can obtain the fixed version from the official GitHub repository or by using the package manager specific to their distribution.
There is no specific workaround mentioned for this vulnerability. It is recommended to apply the fix by updating to the latest version of OpenStack Compute (Nova).
Related vulnerabilities
Recent vulnerabilities recorded for nova.
