CVE-2017-9217

Published: 24 May 2017

systemd-resolved through 233 allows remote attackers to cause a denial of service (daemon crash) via a crafted DNS response with an empty question section.

Priority

Low

CVSS 3 base score: 7.5

Status

Package Release Status
systemd
Launchpad, Ubuntu, Debian
Upstream Needed

Ubuntu 16.04 ESM (Xenial Xerus)
Released (229-4ubuntu19)
Ubuntu 14.04 ESM (Trusty Tahr) Not vulnerable
(204-5ubuntu20.24)
Patches:
Upstream: https://github.com/systemd/systemd/commit/a924f43f30f9c4acaf70618dd2a055f8b0f166be

Notes

AuthorNote
tyhicks
I believe that this was introduced in v223 by
https://github.com/systemd/systemd/commit/29815b6c608b836cada5e349d06a96b63eaa65f3
Lennart pointed out in the pull request that systemd-resolved is
respawned after crashing. Therefore, I've rated this as a low priority.
systemd-resolved became the default DNS resolver in Zesty and it is
enabled in Yakkety
systemd-resolved is not used by default in Xenial. It is spawned if a
user execs the systemd-resolve utility but that shouldn't impact the system.

References

Bugs