CVE-2013-6412: 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…
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.36% (FIRST EPSS).
- No special conditions are required; it is repeatable.
- Fixed version: augeas (Debian:12) 1.2.0-0.1; augeas (Debian:6.0) 0.7.2-1+deb6u1; augeas (Red Hat:enterprise_linux:6::client) 0:1.0.0-5.el6_5.1.
Low priority for now. Upgrade to augeas (Debian:12) 1.2.0-0.1; augeas (Debian:6.0) 0.7.2-1+deb6u1; augeas (Red Hat:enterprise_linux:6::client) 0:1.0.0-5.el6_5.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 22, 2014
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 31th percentile
- CWE
- CWE-264
Report tools
Action score
18
Low priority for now.
- CVSS
- 18 / 40 · 4.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| augeas | augeas | cpe:2.3:a:augeas:augeas |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- augeas augeas1.0.0
- augeas augeas1.1.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | augeas | before 1.2.0-0.1 | 1.2.0-0.1 |
| Debian:6.0 | augeas | before 0.7.2-1+deb6u1 | 0.7.2-1+deb6u1 |
| Red Hat:enterprise_linux:6::client | augeas | before 0:1.0.0-5.el6_5.1 | 0:1.0.0-5.el6_5.1 |
| Red Hat:enterprise_linux:6::client | augeas-debuginfo | before 0:1.0.0-5.el6_5.1 | 0:1.0.0-5.el6_5.1 |
| Red Hat:enterprise_linux:6::client | augeas-devel | before 0:1.0.0-5.el6_5.1 | 0:1.0.0-5.el6_5.1 |
| Red Hat:enterprise_linux:6::client | augeas-libs | before 0:1.0.0-5.el6_5.1 | 0:1.0.0-5.el6_5.1 |
Same product
augeas: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-7555Augeas versions up to and including 1.8.0 are vulnerable to heap-based buffer overflow due to improper handling of escaped strings.41Plan
- CVE-2025-2588Hercules Augeas fa.c re_case_expand null pointer dereference19Monitor
- CVE-2012-0787The clone_file function in transfer.c in Augeas before 1.0.0, when copy_if_rename_fails is set and EXDEV or EBUSY is returned by the rename…14Monitor
Published before and after this one in the same product
- ← EarlierCVE-2012-0786Nov 23, 2013 · The transform_save function in transform.c in Augeas before 1.0.0 allows local users to overwrite arbitrary files and obtain sensitive…13Monitor
- ← EarlierCVE-2012-6607Nov 23, 2013 · The transform_save function in transform.c in Augeas before 1.0.0 allows local users to overwrite arbitrary files and obtain sensitive…13Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:augeas | 1.2.0-0.1 · Debian:12 | Package registry (OSV) |
| red hat:augeas | 0:1.0.0-5.el6_5.1 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:augeas-debuginfo | 0:1.0.0-5.el6_5.1 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:augeas-devel | 0:1.0.0-5.el6_5.1 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:augeas-libs | 0:1.0.0-5.el6_5.1 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-264 · Permissions, Privileges, and Access ControlsCVSS vector
AV:L/AC:L/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.