Skip to content
Fencer Intel
critical 10.0

CVE-2015-3408 json

Module::Signature before 0.74 allows remote attackers to execute arbitrary shell commands via a crafted SIGNATURE file which is not properl…

published 2015-05-19 11 y ago modified 2026-06-17 4 mo ago also EUVD-2015-3452

cvss
10.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.6%
EPSS 5.6% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known

Summary

Module::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.

Patch / fix

  • libmodule-signature-perl Debian 14, Debian 13, Debian 12 0.78-1

debian advisories DEBIAN-CVE-2015-3408

  • libmodule-signature-perl Ubuntu 14.04 LTS 0.73-1ubuntu0.14.04.1

ubuntu advisories UBUNTU-CVE-2015-3408

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • perl-Module-Signature openSUSE Tumbleweed 0.81-1.1

opensuse advisories openSUSE-SU-2024:10458-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-3408 updated cvss 5.1

perl-Module-Signature: arbitrary code execution when verifying module signatures

  • Red Hat Enterprise Linux 7 perl-Module-Signature
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

5.62% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-77 Improper Neutralization of Special Elements used in a Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.