CVE-2018-1160 in the critical feed json
Netatalk before 3.1.12 is vulnerable to an out of bounds write in dsi_opensess.c.
published 7y ago modified 4mo ago also EUVD-2018-11798
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 86.4%
- EPSS 86.4% chance of exploitation in 30 days, percentile 99.7%
- public exploits
- 3
- Exploit-DB
Summary
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.
Patch / fix
- netatalk netatalk 3.1.12
- synology router_manager 1.2-7742-5
- synology diskstation_manager 5.2-5967-9, 6.1.7-15284-3, 6.2.1-23824-4
- netatalk Debian 14, Debian 13 2.2.6-2
debian advisories DEBIAN-CVE-2018-1160
- netatalk Ubuntu 14.04 LTS 2.2.2-1ubuntu2.2
- netatalk Ubuntu 16.04 LTS 2.2.5-1ubuntu0.2
- netatalk Ubuntu 18.04 LTS 2.2.6-1ubuntu0.18.04.2
ubuntu advisories UBUNTU-CVE-2018-1160
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- netatalk SLED 12 SP4, SLED 12 SP3, SLE Workstation Extension 12 SP4 +3 more 3.1.0-3.3.1
- netatalk SLE Software Development Kit 11 SP4 2.0.3-249.23.3.1
suse advisories SUSE-SU-2018:4217-1SUSE-SU-2018:4214-1
- netatalk Alpine 3.24, Alpine 3.23, Alpine 3.22 +14 more 3.1.12-r0
alpine advisories ALPINE-CVE-2018-1160
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2018-1160 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-46048)
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 8mo ago
Exploit prediction
86.42% chance of exploitation in the next 30 days, higher than 99.7% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-46675 QNAP Netatalk < 3.1.12 - Authentication Bypass remote, 2019-04-08
- EDB-46048 Netatalk 3.1.12 - Authentication Bypass (PoC) dos, 2018-12-21
- EDB-46034 Netatalk 3.1.12 - Authentication Bypass remote, 2018-12-21
- tenable.com https://www.tenable.com/security/research/tra-2018-48 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/152440/QNAP-Netatalk-Authentication-Bypass.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- Netatalk Netatalk
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
exploit-db.com
/exploits/46034/
exploit, third-party-advisory, vdb-entry
-
exploit-db.com
/exploits/46048/
exploit, third-party-advisory, vdb-entry
-
exploit-db.com
/exploits/46675/
exploit, third-party-advisory, vdb-entry
-
tenable.com
/security/research/tra-2018-48
exploit, release-notes, third-party-advisory
-
packetstormsecurity.com
/files/152440/QNAP-Netatalk-Authentication-Bypass.html
exploit, third-party-advisory, vdb-entry
-
debian.org
/security/2018/dsa-4356
vendor-advisory, third-party-advisory
-
netatalk.sourceforge.net
/3.1/ReleaseNotes3.1.12.html
release-notes
-
attachments.samba.org
/attachment.cgi?id=14735
third-party-advisory
-
securityfocus.com
/bid/106301
vdb-entry, third-party-advisory
-
github.com
/tenable/poc/tree/master/netatalk/cve_2018_1160/
release-notes, third-party-advisory
-
synology.com
/security/advisory/Synology_SA_18_62
third-party-advisory
Sources
- CVE List CVE-2018-1160
- NVD CVE-2018-1160
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.