CVE-2016-7796
What it is
The manager_dispatch_notify_fd function in systemd allows local users to cause a denial of service (system hang) via a zero-length message received over a notify socket, which causes an error to be returned and the notification handler to be disabled.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.9% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.9% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.9% · EPSS, next 30 days
- Weakness
- CWE-20 · Improper input validation
- Record status
- Modified
Affected
- Systemd Project Systemd 209
- Systemd Project Systemd 213
- Systemd Project Systemd 214
- Systemd Project Systemd 229
- Novell Suse Linux Enterprise Software Development Kit 12.0
- Novell Suse Linux Enterprise Desktop 12
- Novell Suse Linux Enterprise Server 12.0
- Novell Suse Linux Enterprise Server For Sap 12.0
Attack profile CVSS 3.0 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2016-7796.md and follow it. Check whether this project is affected by CVE-2016-7796. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/systemd/systemd/issues/4234#issuecomment-250441246
- https://github.com/systemd/systemd/issues/4234#issuecomment-250441246
References
- http://lists.opensuse.org/opensuse-security-announce/2016-10/msg00015.html
- http://lists.opensuse.org/opensuse-security-announce/2016-10/msg00016.html
- http://rhn.redhat.com/errata/RHSA-2017-0003.html
- http://www.openwall.com/lists/oss-security/2016/09/30/1
- http://www.securityfocus.com/bid/93250
- http://www.securitytracker.com/id/1037320
- https://bugzilla.redhat.com/show_bug.cgi?id=1381911
- https://github.com/systemd/systemd/issues/4234#issuecomment-250441246
- https://rhn.redhat.com/errata/RHBA-2015-2092.html
- https://www.agwa.name/blog/post/how_to_crash_systemd_in_one_tweet
- http://lists.opensuse.org/opensuse-security-announce/2016-10/msg00015.html
- http://lists.opensuse.org/opensuse-security-announce/2016-10/msg00016.html
- http://rhn.redhat.com/errata/RHSA-2017-0003.html
- http://www.openwall.com/lists/oss-security/2016/09/30/1
- http://www.securityfocus.com/bid/93250
- http://www.securitytracker.com/id/1037320
- https://bugzilla.redhat.com/show_bug.cgi?id=1381911
- https://github.com/systemd/systemd/issues/4234#issuecomment-250441246
- https://rhn.redhat.com/errata/RHBA-2015-2092.html
- https://www.agwa.name/blog/post/how_to_crash_systemd_in_one_tweet