Skip to main content
CVE-2024-55564VulnerabilityPublished

CVE-2024-55564: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 0.24 : patch affected systems as a priority.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.24
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

AI-suggested

1. Monitor official POSIX::2008 package repositories and Perl community channels for the release of patches addressing CVE-2024-55564 and apply updates immediately upon availability. 2. In the interim, restrict exposure of Perl environments running vulnerable versions by limiting network access and isolating affected systems. 3. Implement environment variable sanitization and validation to prevent maliciously crafted environment inputs from triggering the buffer overflow. 4. Employ application whitelisting and runtime protection tools to detect and block anomalous code execution attempts originating from Perl processes. 5. Conduct thorough code audits and review usage of POSIX::2008 functions, replacing or refactoring vulnerable calls where feasible. 6. Enhance monitoring and logging around Perl script execution to detect suspicious activity early. 7. Educate development and operations teams about the vulnerability and encourage minimizing reliance on outdated Perl packages. 8. Consider deploying intrusion prevention systems (IPS) with signatures targeting exploitation attempts once available. These steps collectively reduce the attack surface and mitigate risk until a formal patch is released.

Description

The POSIX::2008 package before 0.24 for Perl has a potential _execve50c env buffer overflow.

References

Community reviews

Loading reviews…