Module MetadataPlugin / extension · Module Metadata Project
CVE-2013-1437
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 · uneditedEval injection vulnerability in the Module-Metadata module before 1.000015 for Perl allows remote attackers to execute arbitrary Perl code via the $Version value.
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 confidenceThe Module-Metadata Perl module before version 1.000015 contains an eval injection vulnerability where the $Version variable is not properly sanitized before being passed to eval(), allowing remote attackers to inject and execute arbitrary Perl code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Module MetadataPlugin / extension
< 1.000015
FedoraOperating system
= 18= 19CVSS 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-Metadata is installedRun `perl -MModule::Metadata -e 'print $Module::Metadata::VERSION'` to retrieve the installed version of the Module::Metadata Perl moduleAffected if The command fails (module not installed) or returns a version number less than 1.000015
-
Verify the exact version numberCompare your installed version against the affected range: versions prior to 1.000015 are vulnerableAffected if The installed version is below 1.000015 (for example, 1.000014, 1.000010, or any 1.0xxx version less than 1.000015)
-
Identify if Module-Metadata processes external module filesCheck if your Perl scripts or tools invoke Module::Metadata to parse .pm files from untrusted or third-party sourcesAffected if Module::Metadata is used to parse .pm files where the $Version variable could contain arbitrary content passed to eval()
Your environment is affected if Module::Metadata version 1.000015 or later is NOT installed and the module is used to parse Perl module files containing a $Version variable.
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 · scoped1.000015
Upgrade Module-Metadata to version 1.000015 or later to receive the patched version that properly sanitizes the $Version value before evaluation.
1.000015 or later
- Identify the current version of Module-Metadata installed (e.g., run `perl -MModule::Metadata -e 'print Module::Metadata->new()->version'`)
- Upgrade Module::Metadata to version 1.000015 or later using your Perl module manager (e.g., `cpan Module::Metadata` or `cpanm Module::Metadata`)
- If using system packages on Fedora 18 or 19, update via `yum update perl-Module-Metadata` or wait for the Fedora security update
- Verify the new version is installed: `perl -MModule::Metadata -e 'print Module::Metadata->VERSION' . "\n"'`
- Test that dependent code still functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Module Metadata
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1437 — 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-2013-1437 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