CVE-2011-10043: Module::Load versions before 0.22 for Perl allow arbitrary modules outside of @INC to be loaded
Module::Load versions before 0.22 for Perl allow arbitrary modules outside of @INC to be loaded.
Module names starting with "::" could be passed to the load function to specify arbitrary module paths.
Attackers able to influence module names passed to load could use that bug to execute arbitrary code.
Security readout for executives and security teams
Plain-English summary
A Perl helper library, Module::Load, allowed unsafe module loading before version 0.22. If an attacker can influence the module name an application loads, they may cause unintended code to run. The business risk is highest for Perl services that dynamically load modules from user input, plugins, or untrusted configuration.
Executive priority
Prioritize assessment where Perl applications are internet-facing, multi-tenant, or support user-controlled plugins/configuration. The issue is critical in affected patterns, but not every installation is exploitable.
Technical view
Module::Load before 0.22 accepted module names beginning with "::", enabling paths outside normal @INC resolution to be loaded. The CVE states attackers controlling names passed to load could execute arbitrary code. CVSS is 9.8 critical. Public sources show a 0.22 release and code changes addressing the behavior.
Likely exposure
Exposure is likely limited to Perl applications using vulnerable Module::Load versions and passing attacker-influenced module names into load. Systems using fixed versions, or only loading hardcoded trusted module names, have materially lower exposure.
Exploitation context
No CISA KEV listing or cited source confirms active exploitation. Exploitation requires influence over the module name passed to Module::Load. The primitive is serious because successful abuse can lead to arbitrary code execution in the application context.
Researcher notes
The strongest evidence is the CVE description, MetaCPAN 0.22 release materials, and the 2011 technical blog explaining unsafe interfaces. The source bundle’s affected-version metadata is sparse, so validate actual package versions and code paths rather than relying only on CPE data.
Mitigation direction
Identify Perl applications and dependencies using Module::Load.
Upgrade Module::Load to version 0.22 or later where feasible.
Remove attacker control over module names passed to load.
Restrict plugin or configuration sources to trusted administrators.
Check CPAN/vendor guidance for environment-specific remediation notes.
Validation and detection
Inventory installed Module::Load versions across Perl runtimes.
Review dependency lockfiles, vendored modules, and packaged Perl libraries.
Search application code for dynamic calls to Module::Load load.
Verify module names passed to load are hardcoded or strictly trusted.
Confirm upgraded environments no longer use versions before 0.22.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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 · low confidence lookup
CWE-145: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
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.
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
6Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-145 · source CWE mapping
Improper Neutralization of Section Delimiters
Improper Neutralization of Section Delimiters represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.