Compiler tampering via preserved archive ownership
Published Feb 29, 2024 · Updated Aug 8, 2024
Incorrect file ownership in Daniel Parks puppet-golang before 1.2.7 allows local users to modify Go files installed by root-run Puppet. Root-run tar extraction preserves ownership recorded in affected Go archives instead of applying the user and group declared in Puppet, leaving compiler files assigned to non-root accounts. A local account matching an archived owner can replace the compiler and corrupt software later built or run with greater privileges.
Summary
What happened
Incorrect file ownership in Daniel Parks puppet-golang before 1.2.7 allows local users to modify Go files installed by root-run Puppet. Root-run tar extraction preserves ownership recorded in affected Go archives instead of applying the user and group declared in Puppet, leaving compiler files assigned to non-root accounts. A local account matching an archived owner can replace the compiler and corrupt software later built or run with greater privileges.
The record
- CVE
- CVE-2024-27294
- Published
- Feb 29, 2024
- Updated
- Aug 8, 2024
- Vendor
- Daniel Parks
- Product
- puppet-golang
- Classifications
- CWE-732, T1554
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 29, 2024CVE publishedPublication date reported by the CVE source.
- Aug 8, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.2.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo