Code execution via current-directory module search
Published Apr 1, 2025 · Updated Apr 1, 2025
Uncontrolled search path in Linux::Statm::Tiny before 0.0701 allows attackers to execute code by planting a file in the working directory. The Mite-generated loader searches the current working directory while resolving required Perl code, allowing an attacker-controlled file to replace the intended file. Exploitation requires control of a file in the process working directory and executes that file with the privileges of the importing process.
Summary
What happened
Uncontrolled search path in Linux::Statm::Tiny before 0.0701 allows attackers to execute code by planting a file in the working directory. The Mite-generated loader searches the current working directory while resolving required Perl code, allowing an attacker-controlled file to replace the intended file. Exploitation requires control of a file in the process working directory and executes that file with the privileges of the importing process.
The record
- CVE
- CVE-2025-3051
- Published
- Apr 1, 2025
- Updated
- Apr 1, 2025
- Vendor
- Robert Rothenberg
- Product
- Linux::Statm::Tiny
- Classifications
- CWE-427, T1574
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 1, 2025CVE publishedPublication date reported by the CVE source.
- Apr 1, 2025Record 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 <0.0701
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.
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