Skip to content
Fencer Intel
medium 5.3

CVE-2013-7491 json

An issue was discovered in the DBI module before 1.628 for Perl.

published 6y ago modified 4mo ago also EUVD-2013-7248

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.7%
EPSS 2.7% chance of exploitation in 30 days, percentile 85%
public exploits
0
none known

Summary

An issue was discovered in the DBI module before 1.628 for Perl. Stack corruption occurs when a user-defined function requires a non-trivial amount of memory and the Perl stack gets reallocated.

Patch / fix

  • perl dbi 1.628
  • libdbi-perl Debian 14, Debian 13, Debian 12 1.628-1

debian advisories DEBIAN-CVE-2013-7491

  • perl-DBI SLES 11 SP4-LTSS, SLE Point of Sale 11 SP3 1.607-3.6.1

suse advisories SUSE-SU-2020:14510-1

Is CVE-2013-7491 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-2013-7491 updated cvss 5.7

perl-dbi: Stack corruption on callbacks

  • Red Hat Enterprise Linux 5 perl-DBI Red Hat Enterprise Linux 6 perl-DBI
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 7 perl-DBI
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 8 perl-DBI Red Hat Software Collections rh-perl526-perl-DBI, rh-perl530-perl-DBI
    not affected: vulnerable code not present

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.66% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

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.