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

> An off-by-one error in Netatalk allows heap-based buffer overflows, potentially enabling remote code execution or denial of service.

- **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:** 16 Jun 2024
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2024-38441, GHSA-j764-4v6h-pqp7, GHSA-mj6v-cr68-mj9q, UBUNTU-CVE-2024-38441

## What is CVE-2024-38441?

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

### Official description

Netatalk before 3.2.1 has an off-by-one error and resultant heap-based buffer overflow because of setting ibuf[len] to '\0' in FPMapName in afp_mapname in etc/afpd/directory.c. 2.4.1 and 3.1.19 are also fixed versions.

Weakness: CWE-193 (Off-by-one Error)

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

It affects 1 product.


Products: Netatalk Netatalk.

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

Upgrade to a fixed version.

## Is CVE-2024-38441 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-38439](https://insights.sbomify.com/CVE-2024-38439/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-43634](https://insights.sbomify.com/CVE-2022-43634/): Memory corruption in Netatalk (critical 9.8)
- [CVE-2008-5718](https://insights.sbomify.com/CVE-2008-5718/): Command injection in n/a (critical 9.3)
- [CVE-2024-38440](https://insights.sbomify.com/CVE-2024-38440/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38441 is a critical memory corruption vulnerability in n/a, published on 16 Jun 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-38441 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-38441/ (Markdown: https://insights.sbomify.com/CVE-2024-38441/index.md)
```

## Sources

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

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