Classic Buffer OverflowWeakness · CWE-120

CVE-2024-55564

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The POSIX::2008 Perl module before version 0.24 contains a buffer overflow vulnerability in the _execve50c function related to environment variable handling. This buffer overflow in the env buffer could potentially allow an attacker to execute arbitrary code by overflowing the environment variable storage area when the execve system call wrapper is invoked.

MitigationUpgrade the POSIX::2008 Perl module to version 0.24 or later. If upgrading is not immediately possible, limit or restrict access to functionality that invokes execve with user-controlled environment variables.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed POSIX::2008 Perl module version
    Run 'perl -MPOSIX::2008 -e "print $POSIX::2008::VERSION"' or check via 'cpan -l | grep POSIX::2008'
    Affected if The reported version is less than 0.24 or no version is reported (module may be too old to report version)
  2. Verify execve wrapper usage
    Review application code or scripts that import POSIX::2008 and call execve functions to determine if user-controlled environment variables could be passed
    Affected if The module is used to invoke execve with environment variables that could be influenced by external input

You are affected if the installed POSIX::2008 Perl module version is below 0.24 and your code uses execve with potentially user-controlled environment variables

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the POSIX::2008 Perl module to version 0.24 or later. If upgrading is not immediately possible, limit or restrict access to functionality that invokes execve with user-controlled environment variables.

Recommended fix Moderate confidence

0.24

  1. Check the currently installed version of POSIX::2008 by running: cpan -D POSIX::2008 or cpanm --info POSIX::2008
  2. Upgrade the module to version 0.24 or later using your Perl package manager
  3. For cpanm: run 'cpanm POSIX::2008' or 'cpanm POSIX::[email protected]' to install the specific version
  4. For cpan: run 'cpan POSIX::2008' to install the latest version
  5. Verify the upgrade was successful by checking the installed version again

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-55564 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-55564 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data