# CVE-2011-0012: Path traversal in n/a

> Local attackers can overwrite arbitrary files via a symlink attack on a predictable log file in the SPICE Firefox plugin.

- **Severity:** Low 3.3 (`AV:L/AC:M/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Apr 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pp7j-p833-2h5r

## What is CVE-2011-0012?

CVE-2011-0012 is a low-severity path traversal vulnerability in n/a, published on 18 Apr 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The SPICE Firefox plug-in (spice-xpi) 2.4, 2.3, 2.2, and possibly other versions allows local users to overwrite arbitrary files via a symlink attack on the usbrdrctl log file, which has a predictable name.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2011-0012?

It affects 1 product.


Products: Redhat Spice-Xpi.

## How do I fix CVE-2011-0012?

Apply the vendor's patch.

## Is CVE-2011-0012 being exploited?

There is no known exploitation of CVE-2011-0012 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2011-1179](https://insights.sbomify.com/CVE-2011-1179/): Memory corruption in n/a (medium 5.1)
- [CVE-2010-2792](https://insights.sbomify.com/CVE-2010-2792/): Race condition in n/a (low 3.3)
- [CVE-2010-2794](https://insights.sbomify.com/CVE-2010-2794/): Path traversal in n/a (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-0012 and fix it if it is affected.

What it is: CVE-2011-0012 is a low-severity path traversal vulnerability in n/a, published on 18 Apr 2011. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-0012 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-0012/ (Markdown: https://insights.sbomify.com/CVE-2011-0012/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-0012
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-0012
- OSV: https://osv.dev/vulnerability/CVE-2011-0012

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-0012/
Summaries are generated and may contain mistakes; the official description above is the record.