Skip to content
Fencer Intel
medium 5.0

CVE-2015-3407 json

Module::Signature before 0.74 allows remote attackers to bypass signature verification for files via a signature file that does not list th…

published 11y ago modified 4mo ago also EUVD-2015-3451

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

Summary

Module::Signature before 0.74 allows remote attackers to bypass signature verification for files via a signature file that does not list the files.

Patch / fix

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

debian advisories DEBIAN-CVE-2015-3407

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

ubuntu advisories UBUNTU-CVE-2015-3407

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

Is CVE-2015-3407 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-3407 updated cvss 5.1

perl-Module-Signature: arbitrary code execution during test phase

  • 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

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

CVSS scores

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

Classification

Weakness

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.