Ubuntu LinuxOperating system · Canonical
CVE-2015-3408
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::Signature before 0.74 allows remote attackers to execute arbitrary shell commands via a crafted SIGNATURE file which is not properly handled when generating checksums from a signed manifest.
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::Signature before version 0.74 contains a command injection vulnerability where a crafted SIGNATURE file with malicious content is not properly sanitized when the module generates checksums from a signed manifest. An attacker can embed shell metacharacters into the SIGNATURE file that get executed by the system during checksum verification.
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
Ubuntu LinuxOperating system
= 12.04= 14.04= 14.10= 15.04<= 0.73CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Verify Module::Signature is installedRun `perl -MModule::Signature -e 'print $Module::Signature::VERSION'` or check via `cpan -l | grep Module::Signature`Affected if Module::Signature is not installed or the command fails - the vulnerability does not apply
-
Check installed version of Module::SignatureCompare the version number obtained from the previous step to the affected range: versions 0.73 and earlier are vulnerable, version 0.74 and later are fixedAffected if Version is 0.73 or earlier
-
Determine if SIGNATURE file processing occursCheck for presence of SIGNATURE files in Perl module directories or in project directories: look for files named 'SIGNATURE' in directories containing Perl modules, or check if the perl modules on the system include any SIGNATURE filesAffected if SIGNATURE files exist and are processed by Module::Signature; the command injection only triggers when checksums are generated from a signed manifest
You are affected if Module::Signature version 0.73 or earlier is installed AND SIGNATURE files are being processed on your system.
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::Signature to version 0.74 or later. If upgrading is not immediately possible, avoid processing SIGNATURE files from untrusted sources and implement input validation on any SIGNATURE files before they are processed.
Module::Signature 0.74 or later
- Install the latest version of Module::Signature from CPAN using: cpan Module::Signature
- Or upgrade via system package manager if available (e.g., apt-get update && apt-get install libmodule-signature-perl on Ubuntu/Debian)
- Verify the installed version is >= 0.74 using: perl -MModule::Signature -e 'print $Module::Signature::VERSION'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ubuntu Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.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-2015-3408 — 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-2015-3408 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