Debian LinuxOperating system · Debian
CVE-2022-23125
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 · uneditedThis vulnerability allows remote attackers to execute arbitrary code on affected installations of Netatalk. Authentication is not required to exploit this vulnerability. The specific flaw exists within the copyapplfile function. When parsing the len element, the process does not properly validate the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-15869.
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 · high confidenceA stack-based buffer overflow vulnerability in Netatalk's copyapplfile function allows remote unauthenticated attackers to execute arbitrary code as root by supplying overly long data in the len element, which is copied to a fixed-length stack buffer without proper length validation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Debian LinuxOperating system
= 10.0= 11.0< 3.1.13CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Netatalk is installedRun 'which afpd' or check package manager output (e.g., 'dpkg -l | grep netatalk' on Debian)Affected if Netatalk is not found on the system, then the vulnerability does not apply
-
Determine installed Netatalk versionRun 'afpd -v' or 'netatalk -v' to obtain the version numberAffected if The version is lower than 3.1.13 (e.g., 3.1.12, 3.1.11, etc.)
-
Check if AFP service is enabled or runningRun 'systemctl status afpd' or check for afpd process with 'ps aux | grep afpd'Affected if AFP daemon (afpd) is actively running or enabled to start at boot, making the vulnerable code reachable over the network
-
Confirm AppleTalk/AFP network listeningInspect network listening ports with 'ss -tlnp | grep afp' or 'netstat -tlnp | grep 548' (AFP default port 548)Affected if Port 548 (AFP) or other AppleTalk ports are listening on network interfaces, indicating the service is exposed to potential remote attack
A system is affected if Netatalk version is below 3.1.13 AND the AFP service is running and network-accessible, enabling remote attackers to trigger the buffer overflow via the copyapplfile function with oversized len data.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.1.13
Apply the vendor patch for CVE-2022-23125 to the affected Netatalk installation, or upgrade to a patched version. If patching is not immediately possible, restrict network access to AFP services.
Netatalk 3.1.13 or later
- 1. Update the Debian package repository index: sudo apt update
- 2. Upgrade Netatalk to the fixed version: sudo apt upgrade netatalk
- 3. Verify the installed version is 3.1.13 or later: dpkg -l | grep netatalk
- 4. Restart the Netatalk service to apply the fix: sudo systemctl restart netatalk
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23125 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-23125 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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