CVE-2011-10043
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 · uneditedModule::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.
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 confidenceModule::Load before version 0.22 allows loading arbitrary Perl modules outside of @INC by prefixing module names with '::', enabling path traversal. Attackers who can control module names passed to the load() function can execute arbitrary code by loading and executing malicious modules.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check if Module::Load is installedRun `perl -MModule::Load -e 'print "Module::Load is installed\n"'` or list it in the system perl libraryAffected if Module::Load is not installed means the vulnerability does not apply
-
Determine the installed version of Module::LoadRun `perl -MModule::Load -e 'print $Module::Load::VERSION'` to print the version numberAffected if The version is less than 0.22 (e.g., 0.21, 0.20, or any version without a number shown)
-
Identify code using Module::Load with potentially untrusted inputSearch Perl source code for calls to Module::Load::load or the 'use Module::Load' pattern where module names could be derived from user input, CGI parameters, or external configurationAffected if User-controlled or external input can reach the module name parameter in Module::Load functions without validation
You are affected if Module::Load version is below 0.22 AND your code passes untrusted or user-controlled input to the load function without validating that module names do not start with '::'.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Module::Load to version 0.22 or later. Review code paths where user-controlled input influences module loading to prevent exploitation.
Module::Load version 0.22
- Upgrade Module::Load to version 0.22 or later
- If using CPAN: run 'cpan Module::Load' or 'cpanm Module::Load'
- If using system package manager (e.g., apt, yum), update the perl-Module-Load package to the latest version
- Verify the upgrade was successful by checking the installed version: 'perl -MModule::Load -e 'print $Module::Load::VERSION'"
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-10043 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-10043 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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