Code execution via current-directory Perl module loading
Published Feb 19, 2022 · Updated Sep 16, 2024
Code execution in Debian duck before 0.10 allows local users to run arbitrary Perl code when duck starts in an attacker-controlled directory. At startup, duck lets Perl resolve required modules through the current working directory, so a same-named attacker file loads instead of the intended module. Exploitation requires write access to that directory and execution of duck there; injected code inherits the invoking user's privileges.
Summary
What happened
Code execution in Debian duck before 0.10 allows local users to run arbitrary Perl code when duck starts in an attacker-controlled directory. At startup, duck lets Perl resolve required modules through the current working directory, so a same-named attacker file loads instead of the intended module. Exploitation requires write access to that directory and execution of duck there; injected code inherits the invoking user's privileges.
The record
- CVE
- CVE-2016-1239
- Published
- Feb 19, 2022
- Updated
- Sep 16, 2024
- Vendor
- Debian
- Product
- duck
- Classifications
- T1574
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 19, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=< 0.10
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
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