LiveActive security incident?Get immediate response
CVE Record

CVE-2011-10007: File::Find::Rule through 0.34 for Perl is vulnerable to Arbitrary Code Execution when `grep()` encounters a crafted file name

File::Find::Rule through 0.34 for Perl is vulnerable to Arbitrary Code Execution when `grep()` encounters a crafted filename. A file handle is opened with the 2 argument form of `open()` allowing an attacker controlled filename to provide the MODE parameter to `open()`, turning the filename into a command to be executed. Example: $ mkdir /tmp/poc; echo > "/tmp/poc/|id" $ perl -MFile::Find::Rule \     -E 'File::Find::Rule->grep("foo")->in("/tmp/poc")' uid=1000(user) gid=1000(user) groups=1000(user),100(users)

HighCVSS 8.8Not KEV-listedUpdated
Glexia's Takehigh

Analyst readout for executives and security teams

Plain-English summary

A Perl file-search library can run attacker-controlled commands if an application scans a directory containing a maliciously named file. The business risk is highest where Perl automation or web backends process attacker-writable directories. Sources do not show known active exploitation or CISA KEV listing.

Executive priority

Treat as high priority for Perl-heavy environments, especially legacy automation and services handling uploads or shared files. Prioritize internet-facing or multi-user systems first. Lower urgency is reasonable where File::Find::Rule is absent or only scans trusted, administrator-controlled directories.

Technical view

File::Find::Rule through 0.34 uses Perl's unsafe two-argument open in grep() handling. A crafted filename can be interpreted as the open mode and execute as a command. The issue is classified as CWE-78 with CVSS 3.1 score 8.8 and requires an application to invoke grep() on attacker-influenced filenames.

Likely exposure

Exposure is likely limited to systems using the CPAN File-Find-Rule package or downstream distro package where File::Find::Rule->grep() scans directories writable or influenceable by attackers. Exact fixed downstream versions are not fully enumerated in the provided bundle.

Exploitation context

The CVE bundle includes public proof-of-concept detail and an issue reference tagged exploit, but KEV is false and no cited source states active exploitation. Practical exploitation depends on an attacker placing or influencing filenames that a vulnerable Perl process later scans.

Researcher notes

The vulnerability is in filename handling, not file contents. Validate reachability through application call paths using grep(), directory trust boundaries, and runtime privileges. The supplied affected metadata is sparse, so confirm package names and fixed versions with each distribution or vendor advisory.

Mitigation direction

  • Inventory File-Find-Rule and File::Find::Rule versions in Perl applications and hosts.
  • Upgrade to a vendor or distribution release containing the upstream patch.
  • Apply the referenced upstream patch where no packaged fix is available.
  • Avoid using grep() on attacker-writable directories until patched.
  • Restrict write access to directories scanned by vulnerable Perl jobs.

Validation and detection

  • Check dependency manifests and package inventories for File-Find-Rule through 0.34.
  • Find File::Find::Rule->grep() usage in application and operations code.
  • Confirm whether scanned directories can contain attacker-controlled filenames.
  • Verify patched source no longer uses unsafe two-argument open for grep file reads.
  • Run regression tests for file scanning behavior after updating.
Prepared
Confidence
high
Sources
10

Based on public source material and reviewed before publication.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-78: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2011-10007 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2011-10007Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
RCLAMPFile::Find::RuleFile-Find-Rule, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-78 · source CWE mapping

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.