# CVE-2022-43634: Memory corruption in Netatalk

> Remote attackers can execute arbitrary code as root on Netatalk servers via a heap buffer overflow in the dsi_writeinit function without authentication.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 29 Mar 2023
- **Updated:** 12 Feb 2025
- **Also known as:** DEBIAN-CVE-2022-43634, GHSA-fwj9-7qq8-jc93, SUSE-SU-2023:0316-1, UBUNTU-CVE-2022-43634

## What is CVE-2022-43634?

CVE-2022-43634 is a critical memory corruption vulnerability in Netatalk, published on 29 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This 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 dsi_writeinit function. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-17646.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2022-43634?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `netatalk` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 3.1.0-3.14.1 |
| `netatalk` | SUSE:Linux Enterprise Workstation Extension 12 SP5 | All versions | 3.1.0-3.14.1 |

Products: Netatalk Netatalk.

## How do I fix CVE-2022-43634?

Apply the vendor's patch.

## Is CVE-2022-43634 being exploited?

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

## Other vulnerabilities in Netatalk

- [CVE-2024-38439](https://insights.sbomify.com/CVE-2024-38439/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-38441](https://insights.sbomify.com/CVE-2024-38441/): Memory corruption in n/a (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-2022-43634 and fix it if it is affected.

What it is: CVE-2022-43634 is a critical memory corruption vulnerability in Netatalk, published on 29 Mar 2023. 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-2022-43634 in the wild and no public exploit code.

Affected product: Netatalk. 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-2022-43634/ (Markdown: https://insights.sbomify.com/CVE-2022-43634/index.md)
```

## Sources

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

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