USN-3466-1: systemd vulnerability
26 October 2017
systemd could be made to temporarily stop responding if it received specially crafted network traffic.
Releases
Packages
- systemd - system and service manager
Details
Karim Hossen & Thomas Imbert and Nelson William Gamazo Sanchez
independently discovered that systemd-resolved incorrectly
handled certain DNS responses. A remote attacker could possibly use this
issue to cause systemd to temporarily stop responding, resulting in a
denial of service.
Update instructions
The problem can be corrected by updating your system to the following package versions:
Ubuntu 17.10
Ubuntu 17.04
In general, a standard system update will make all the necessary changes.
References
Related notices
- USN-3558-1: libnss-myhostname, systemd-coredump, libsystemd-daemon0, libudev1, systemd-services, libsystemd-login-dev, udev-udeb, libnss-resolve, libudev1-udeb, libsystemd-daemon-dev, libsystemd-journal0, systemd, libsystemd-login0, systemd-sysv, libsystemd-journal-dev, libgudev-1.0-0, libgudev-1.0-dev, udev, libnss-mymachines, libudev-dev, libsystemd-dev, libpam-systemd, systemd-journal-remote, libsystemd-id128-dev, libsystemd0, python-systemd, systemd-container, gir1.2-gudev-1.0, libsystemd-id128-0