CVE-2012-3360
Summary
| CVE | CVE-2012-3360 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2012-07-22 16:55:00 UTC |
| Updated | 2012-08-17 03:53:00 UTC |
| 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. |
Risk And Classification
Problem Types: CWE-22
NVD Known Affected Configurations (CPE 2.3)
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Security Advisory SA49763 - OpenStack Compute (Nova) Host File Injection and File Corruption Vulnerabilities - Secunia | SECUNIA | secunia.com | Vendor Advisory |
| Prevent file injection writing to host filesystem. · b0feaff · openstack/nova · GitHub | CONFIRM | github.com | Exploit, Patch |
| OpenStack Nova CVE-2012-3360 Remote Code Injection Vulnerability | BID | www.securityfocus.com | |
| [SECURITY] Fedora 17 Update: openstack-nova-2012.1.1-3.fc17 | FEDORA | lists.fedoraproject.org | |
| Prevent file injection writing to host filesystem. · 2427d4a · openstack/nova · GitHub | CONFIRM | github.com | |
| USN-1497-1: Nova vulnerabilities | Ubuntu | UBUNTU | www.ubuntu.com | |
| Bug #1015531 “Remote arbitrary file corruption / creation flaw v...” : Bugs : OpenStack Compute (nova) | CONFIRM | bugs.launchpad.net | |
| [OSSA 2012-008] Arbitrary file injection/corruption through directory traversal issues (CVE-2012-3360, CVE-2012-3361) : Mailing list archive : openstack team in Launchpad | MLIST | lists.launchpad.net | |
| Security Advisory SA49802 - Ubuntu update for nova - Secunia | SECUNIA | secunia.com | Vendor Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.