CVE-2024-38441: netatalk · Off-by-one Error
Affects netatalkSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in 3.2.1 : patch netatalk as a priority.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.2.1, 3.1.19, 2.4.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Upgrade netatalk/netatalk to 3.2.1, 3.1.19 or 2.4.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubnetatalk/netatalkpkg:github/netatalk/netatalkOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-38441, European organizations should immediately upgrade Netatalk installations to version 3.2.1 or later, or apply backported patches available in versions 2.4.1 and 3.1.19. Where immediate patching is not feasible, organizations should restrict AFP service exposure by implementing network segmentation and firewall rules to limit access to trusted hosts only. Disabling AFP services on systems where it is not required can reduce the attack surface. Monitoring network traffic for unusual AFP activity and deploying intrusion detection systems capable of recognizing exploitation attempts can provide early warning. Additionally, organizations should review and harden system configurations, including applying least privilege principles to AFP service accounts and ensuring secure coding practices in custom AFP extensions or scripts. Regular vulnerability scanning and penetration testing focused on AFP services will help identify residual risks. Finally, maintaining up-to-date backups is essential to recover from potential compromises.
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.
References
- github.com/Netatalk/netatalk/issues/1098 (opens in a new tab)
- github.com/Netatalk/netatalk/blob/90d91a9ac9a7d6132ab7620d31c8c23400949206/etc/afpd/directory.c (opens in a new tab)
- github.com/Netatalk/netatalk/security/advisories/GHSA-mj6v-cr68-mj9q (opens in a new tab)
- netatalk.io/security/CVE-2024-38441 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2024/11/msg00026.html (opens in a new tab)