dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2025-3051

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Linux::Statm::Tiny for Perl before 0.0701 allows untrusted code from the current working directory ('.') to be loaded similar to CVE-2016-1238. If an attacker can place a malicious file in current working directory, it may be loaded instead of the intended file, potentially leading to arbitrary code execution. Linux::Statm::Tiny uses Mite to produce the affected code section due to CVE-2025-30672

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Linux::Statm::Tiny Perl module before 0.0701 has an insecure module loading vulnerability where it may load untrusted code from the current working directory ('.') due to how Mite handles module path resolution. If an attacker can place a malicious Perl module with a matching name in the application's CWD, it will be loaded instead of the intended module, leading to arbitrary code execution.

MitigationUpgrade Linux::Statm::Tiny to version 0.0701 or later. Additionally, ensure Perl applications do not run from directories where untrusted users can write files, and avoid using '.' in @INC.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Linux::Statm::Tiny is installed
    Run 'perl -MLinux::Statm::Tiny -e "print $Linux::Statm::Tiny::VERSION"' or check your system's Perl module directory for the Linux/Statm/Tiny.pm file
    Affected if The module is not installed - not affected. If installed, proceed to version check.
  2. Determine the installed version
    Run 'perl -MLinux::Statm::Tiny -e "print $Linux::Statm::Tiny::VERSION"' to print the version number, or use 'cpan -D Linux::Statm::Tiny'
    Affected if Version is less than 0.0701 - vulnerable to arbitrary code execution via CWD module injection.
  3. Verify the module is actually loaded by your application
    Search your application code for 'use Linux::Statm::Tiny' or 'require Linux::Statm::Tiny' statements, or run the application and check loaded modules with 'perl -MModule::Loaded -e '
    Affected if The module is loaded at runtime - the vulnerability can be triggered.
  4. Check the Perl @INC for '.' inclusion
    Run 'perl -e "print join("\n", @INC)"' to see if the current working directory is in the module search path
    Affected if '.' is present in @INC - the vulnerable code path is active.

You are affected if Linux::Statm::Tiny version 0.0701 or later is NOT installed AND your application loads this module AND '.' is in @INC (the default Perl behavior), allowing an attacker who can write to your working directory to execute arbitrary code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Linux::Statm::Tiny to version 0.0701 or later. Additionally, ensure Perl applications do not run from directories where untrusted users can write files, and avoid using '.' in @INC.

Recommended fix High confidence

Linux::Statm::Tiny version 0.0701 or later

  1. Verify current version: perl -MLinux::Statm::Tiny -e 'print $Linux::Statm::Tiny::VERSION'
  2. Upgrade the module using cpan: cpan Linux::Statm::Tiny
  3. Or upgrade using cpanm: cpanm Linux::Statm::Tiny
  4. Verify the fix by checking the new version matches 0.0701 or later: perl -MLinux::Statm::Tiny -e 'print $Linux::Statm::Tiny::VERSION'
Caveat Minor version upgrade; unlikely to have breaking changes, but test your application after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3051 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3051 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data