cve.bz

CVE-2004-2022 activestate activeperl

no score yetExploitEPSS 1.7%

activestate activeperl: no CVSS score yet. EPSS 1.7% estimated probability of exploitation activity in the next 30 days.

On this page
ActivePerl 5.8.x and others, and Larry Wall's Perl 5.6.1 and others, when running on Windows systems, allows attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long argument to the system command, which leads to a stack-based buffer overflow. NOTE: it is unclear whether this bug is in Perl or the OS API that is used by Perl.
EPSS
1.7% (unchanged from 1.7% a week ago; 1.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 78th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2004-2022 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2004-2022?via=ask-ai-copy and https://cve.bz/cve/CVE-2004-2022?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2004-2022 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
activestate:activeperl5.6.1
activestate:activeperl5.6.1.630
activestate:activeperl5.6.2
activestate:activeperl5.6.3
activestate:activeperl5.7.1
activestate:activeperl5.7.2
activestate:activeperl5.7.3
activestate:activeperl5.8

Public exploits

References

Check your stackJSON