Local file redirection via unsafe symlink traversal
Published Jan 31, 2020 · Updated Aug 7, 2024
Improper link resolution in Perl File::Temp allows local users to redirect temporary file creation through attacker-owned symlinks. The _is_safe routine accepts a path whose symlink or hardlink chain traverses directories not owned by root or the calling user. Exploitation requires local filesystem access and a more privileged process using that path, enabling attacker-directed file placement or modification.
Summary
What happened
Improper link resolution in Perl File::Temp allows local users to redirect temporary file creation through attacker-owned symlinks. The _is_safe routine accepts a path whose symlink or hardlink chain traverses directories not owned by root or the calling user. Exploitation requires local filesystem access and a more privileged process using that path, enabling attacker-directed file placement or modification.
The record
- CVE
- CVE-2011-4116
- Published
- Jan 31, 2020
- Updated
- Aug 7, 2024
- Vendor
- Perl
- Product
- File::Temp
- Classifications
- CWE-59
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 31, 2020CVE publishedPublication date reported by the CVE source.
- Aug 7, 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=unknown
What conditions does exploitation require?
What is affected?
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
- File::Temp attacker-owned symlink demonstrationproof of concept · demonstrated
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