# CVE-2018-1160: Memory corruption in Netatalk

> A remote unauthenticated attacker can achieve arbitrary code execution via an out-of-bounds write in Netatalk due to missing bounds checking.

- **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:** 20 Dec 2018
- **Updated:** 13 Feb 2026
- **Also known as:** DEBIAN-CVE-2018-1160, DSA-4356-1, GHSA-j675-7hvj-qfw5, MGASA-2019-0061, SUSE-SU-2018:4214-1, SUSE-SU-2018:4217-1, UBUNTU-CVE-2018-1160

## What is CVE-2018-1160?

CVE-2018-1160 is a critical memory corruption vulnerability in Debian Debian Linux, published on 20 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Netatalk before 3.1.12 is vulnerable to an out of bounds write in dsi_opensess.c. This is due to lack of bounds checking on attacker controlled data. A remote unauthenticated attacker can leverage this vulnerability to achieve arbitrary code execution.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2018-1160?

It affects 6 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `netatalk` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 3.1.0-3.3.1 |
| `netatalk` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 3.1.0-3.3.1 |
| `netatalk` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 2.0.3-249.23.3.1 |
| `netatalk` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 3.1.0-3.3.1 |
| `netatalk` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 3.1.0-3.3.1 |
| `netatalk` | SUSE:Linux Enterprise Workstation Extension 12 SP3 | All versions | 3.1.0-3.3.1 |
| `netatalk` | SUSE:Linux Enterprise Workstation Extension 12 SP4 | All versions | 3.1.0-3.3.1 |

Products: Debian Debian Linux, Netatalk Netatalk, Synology Diskstation Manager, Synology Router Manager, Synology Skynas, Synology Vs960hd Firmware.

## How do I fix CVE-2018-1160?

Upgrade to a fixed version.

## Is CVE-2018-1160 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-1160 exists.

Public exploit code:

- Netatalk 3.1.12 - Authentication Bypass (exploitdb)
- Netatalk 3.1.12 - Authentication Bypass (PoC) (exploitdb)
- QNAP Netatalk < 3.1.12 - Authentication Bypass (exploitdb)
- https://github.com/SachinThanushka/CVE-2018-1160 (github_poc): https://github.com/SachinThanushka/CVE-2018-1160

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1160 and fix it if it is affected.

What it is: CVE-2018-1160 is a critical memory corruption vulnerability in Debian Debian Linux, published on 20 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-1160 exists.

Affected product: Debian Debian Linux. 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-2018-1160/ (Markdown: https://insights.sbomify.com/CVE-2018-1160/index.md)
```

## Sources

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

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