# CVE-2012-6607: Path traversal in n/a

> Local attackers can overwrite arbitrary files and read sensitive data via symlink attacks in Augeas backup operations.

- **Severity:** Low 3.3 (`AV:L/AC:M/Au:N/C:P/I:P/A:N`)
- **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:** 23 Nov 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-6607, GHSA-2x6r-rq7f-fcrj

## What is CVE-2012-6607?

CVE-2012-6607 is a low-severity path traversal vulnerability in n/a, published on 23 Nov 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The transform_save function in transform.c in Augeas before 1.0.0 allows local users to overwrite arbitrary files and obtain sensitive information via a symlink attack on a .augsave file in a backup save action, a different vector than CVE-2012-0786.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2012-6607?

It affects 1 product.


Products: Augeas Augeas.

## How do I fix CVE-2012-6607?

Upgrade to a fixed version.

## Is CVE-2012-6607 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-7555](https://insights.sbomify.com/CVE-2017-7555/): Memory corruption in augeas (critical 9.8)
- [CVE-2025-2588](https://insights.sbomify.com/CVE-2025-2588/): Hercules Augeas fa.c re_case_expand null pointer dereference (medium 4.8)
- [CVE-2013-6412](https://insights.sbomify.com/CVE-2013-6412/): Misconfiguration in n/a (medium 4.6)
- [CVE-2012-0787](https://insights.sbomify.com/CVE-2012-0787/): Race condition in n/a (low 3.7)
- [CVE-2012-0786](https://insights.sbomify.com/CVE-2012-0786/): Path traversal in n/a (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6607 and fix it if it is affected.

What it is: CVE-2012-6607 is a low-severity path traversal vulnerability in n/a, published on 23 Nov 2013. 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-2012-6607 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-2012-6607/ (Markdown: https://insights.sbomify.com/CVE-2012-6607/index.md)
```

## Sources

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

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