What is CVE-2018-1160?A critical-severity flaw in Netatalk, explained.
CVE-2018-1160 is a critical-severity flaw (CVSS 9.8) in Netatalk, published on 20 December 2018. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 87%. If you run an affected version, plan in the vendor’s fix.
Published 20 December 2018. Record last updated 14 January 2025. We keep this page's data up to date.
What is CVE-2018-1160? In plain terms.
It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
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.
What kind of flaw is it?
- CWE-787Out-of-bounds Write
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data, change data and take it offline
Severity vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is CVE-2018-1160 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 87%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2018-1160 scores 78. Action: Patch now.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2018-1160 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2018-1160? 7 products.
The published record lists 7 products from 3 vendors. Versions are shown as published: "before 3.1.12" means every version up to, but not including, 3.1.12. If you run one of these, check your version, then go to the fix below.
- Application
Netatalk
by Netatalk
Affected versionsbefore 3.1.12 - Operating system
Diskstation Manager
by Synology
Affected versions5.2 to before 5.2-5967-96.1 to before 6.1.7-15284-36.2 to before 6.2.1-23824-4 - Operating system
Debian Linux
by Debian
Affected versions9.0 - Application
Router Manager
by Synology
Affected versions1.2 to before 1.2-7742-5 - Application
Skynas
by Synology
Affected versionsversion not specified - Hardware
Vs960hd
by Synology
Affected versionsversion not specified - Operating system
Vs960hd Firmware
by Synology
Affected versionsversion not specified
How do I fix CVE-2018-1160? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the latest update from the vendor. The references list where the vendor has published details.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
References
11 links- ReleaseNotes3.1.12 (opens in a new tab)sourceforge.net
- QNAP Netatalk Authentication Bypass (opens in a new tab)packetstormsecurity.com
- Web page (opens in a new tab)securityfocus.com
- Attachment.cgi (opens in a new tab)samba.org
- tenable/poc code (opens in a new tab)github.com
- Dsa 4356 (opens in a new tab)debian.org · 2018
Does CVE-2018-1160 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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 remot...
- Matched to
- Netatalk on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2018-1160 is a critical-severity flaw in Netatalk, published on 20 December 2018. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
It scores 9.8 out of 10 on the CVSS severity scale, which is critical. Our risk score for CVE-2018-1160 is 78 out of 100, which is High. Its action is "Patch now". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 87%. That can change at any time, which is why we keep watching.
For Netatalk: before 3.1.12. The record lists 7 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.