# CVE-2024-55564: Memory corruption in n/a

> A buffer overflow in the Perl POSIX::2008 module allows attackers to execute arbitrary code via crafted environment variables.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Dec 2024
- **Updated:** 9 Dec 2024
- **Also known as:** DEBIAN-CVE-2024-55564, GHSA-5gjq-58c4-9ff5, UBUNTU-CVE-2024-55564

## What is CVE-2024-55564?

CVE-2024-55564 is a critical memory corruption vulnerability in n/a, published on 9 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2024-55564?


## How do I fix CVE-2024-55564?

Upgrade to a fixed version.

## Is CVE-2024-55564 being exploited?

There is no known exploitation of CVE-2024-55564 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-55564 and fix it if it is affected.

What it is: CVE-2024-55564 is a critical memory corruption vulnerability in n/a, published on 9 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-55564 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-55564/ (Markdown: https://insights.sbomify.com/CVE-2024-55564/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-55564
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-55564
- OSV: https://osv.dev/vulnerability/CVE-2024-55564

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-55564/
Summaries are generated and may contain mistakes; the official description above is the record.