# CVE-2013-6412: Misconfiguration in n/a

> Local attackers can modify files due to incorrect permission calculations when the umask contains a 7, affecting the Augeas configuration library.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/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:** 23 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-6412, GHSA-92m6-rfw4-wpq6, RHSA-2014:0044

## What is CVE-2013-6412?

CVE-2013-6412 is a medium-severity vulnerability in n/a, published on 23 Jan 2014. 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 1.0.0 through 1.1.0 does not properly calculate the permission values when the umask contains a "7," which causes world-writable permissions to be used for new files and allows local users to modify the files via unspecified vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2013-6412?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `augeas` | Red Hat:enterprise_linux:6::client | All versions | 0:1.0.0-5.el6_5.1 |
| `augeas-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:1.0.0-5.el6_5.1 |
| `augeas-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:1.0.0-5.el6_5.1 |
| `augeas-libs` | Red Hat:enterprise_linux:6::client | All versions | 0:1.0.0-5.el6_5.1 |
| `augeas` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.0.0-5.el6_5.1 |
| `augeas-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.0.0-5.el6_5.1 |
| `augeas-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.0.0-5.el6_5.1 |
| `augeas-libs` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.0.0-5.el6_5.1 |
| `augeas` | Red Hat:enterprise_linux:6::server | All versions | 0:1.0.0-5.el6_5.1 |
| `augeas-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:1.0.0-5.el6_5.1 |
| `augeas-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:1.0.0-5.el6_5.1 |
| `augeas-libs` | Red Hat:enterprise_linux:6::server | All versions | 0:1.0.0-5.el6_5.1 |
| `augeas` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.0.0-5.el6_5.1 |
| `augeas-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.0.0-5.el6_5.1 |
| `augeas-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.0.0-5.el6_5.1 |
| `augeas-libs` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.0.0-5.el6_5.1 |

Products: Augeas Augeas.

## How do I fix CVE-2013-6412?

Upgrade to a fixed version.

## Is CVE-2013-6412 being exploited?

There is no known exploitation of CVE-2013-6412 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-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)
- [CVE-2012-6607](https://insights.sbomify.com/CVE-2012-6607/): Path traversal in n/a (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6412 and fix it if it is affected.

What it is: CVE-2013-6412 is a medium-severity vulnerability in n/a, published on 23 Jan 2014. 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-2013-6412 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-2013-6412/ (Markdown: https://insights.sbomify.com/CVE-2013-6412/index.md)
```

## Sources

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

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