Skip to content
Noroxi
CVE-2005-3962· NVD / CVE Program· CNA redhat

Integer overflow in the format string functionality (Perl_sv_vcatpvfn) in Perl 5.9.2 and 5.8.6 Perl allows attackers to overwrite arbitrary

Integer overflow in the format string functionality (Perl_sv_vcatpvfn) in Perl 5.9.2 and 5.8.6 Perl allows attackers to overwrite arbitrary memory and possibly execute arbitrary code via format string specifiers with large values, which causes an integer wrap and leads to a buffer overflow, as demonstrated using format string vulnerabilities in Perl applications.

MediumCVSS 4.6 · v2.0—No exploit Fix available
Published
Dec 1, 2005
Updated
Jun 16, 2026
EPSS
1.4% · 71th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.6 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.4%

Affected systems

VendorProduct
perlperl

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • perl perl5.8.6
  • perl perl5.9.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12perlbefore 5.8.7-95.8.7-9
Debian:3.1perlbefore 5.8.4-8sarge35.8.4-8sarge3
openSUSE:Tumbleweedperlbefore 5.34.0-1.15.34.0-1.1
Red Hat:enterprise_linux:3::asperlbefore 2:5.8.0-90.42:5.8.0-90.4
Red Hat:enterprise_linux:3::asperl-CGIbefore 2:2.89-90.42:2.89-90.4
Red Hat:enterprise_linux:3::asperl-CPANbefore 2:1.61-90.42:1.61-90.4
Red Hat:enterprise_linux:3::asperl-DB_Filebefore 2:1.806-90.42:1.806-90.4
Red Hat:enterprise_linux:3::asperl-suidperlbefore 2:5.8.0-90.42:5.8.0-90.4
Red Hat:enterprise_linux:4::asperlbefore 3:5.8.5-24.RHEL43:5.8.5-24.RHEL4
Red Hat:enterprise_linux:4::asperl-debuginfobefore 3:5.8.5-24.RHEL43:5.8.5-24.RHEL4
Red Hat:enterprise_linux:4::asperl-suidperlbefore 3:5.8.5-24.RHEL43:5.8.5-24.RHEL4

Same product

perl: all records

Other highest-scoring records for the same primary product.

  • CVE-2012-6329The _compile function in Maketext.pm in the Locale::Maketext implementation in Perl before 5.17.7 does not properly handle backslashes and f
    49Plan
  • CVE-2018-18311Perl before 5.26.3 and 5.28.x before 5.28.1 has a buffer overflow via a crafted regular expression that triggers invalid write operations.
    43Plan
  • CVE-2018-18312Perl before 5.26.3 and 5.28.0 before 5.28.1 has a buffer overflow via a crafted regular expression that triggers invalid write operations.
    43Plan
  • CVE-2018-6913Heap-based buffer overflow in the pack function in Perl before 5.26.2 allows context-dependent attackers to execute arbitrary code via a lar
    42Plan
  • CVE-2018-18314Perl before 5.26.3 has a buffer overflow via a crafted regular expression that triggers invalid write operations.
    41Plan
  • CVE-2018-6797An issue was discovered in Perl 5.18 through 5.26.
    41Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:perl5.8.7-9 · Debian:12Package registry (OSV)
opensuse:perl5.34.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:perl3:5.8.5-24.RHEL4 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:perl-CGI2:2.89-90.4 · Red Hat:enterprise_linux:3::asPackage registry (OSV)
red hat:perl-CPAN2:1.61-90.4 · Red Hat:enterprise_linux:3::asPackage registry (OSV)
red hat:perl-DB_File2:1.806-90.4 · Red Hat:enterprise_linux:3::asPackage registry (OSV)
red hat:perl-debuginfo3:5.8.5-24.RHEL4 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:perl-suidperl3:5.8.5-24.RHEL4 · Red Hat:enterprise_linux:4::asPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
P · data can be read
Integrity
P · data or configuration can be modified
Availability
P · the service can be disrupted
Attack complexity
Low
Confidentiality impact
P
Integrity impact
P
Availability impact
P

Weakness class (CWE)

CWE-189 · Numeric Errors

CVSS vector

AV:L/AC:L/Au:N/C:P/I:P/A:P

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records