CVE-2017-9217

Publication date 24 May 2017

Last updated 24 July 2024

Ubuntu priority

Cvss 3 Severity Score

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.

Read the notes from the security team

Status

Show unmaintained releases

Package	Ubuntu Release	Status
systemd	17.04 zesty	Fixed 232-21ubuntu4
	16.10 yakkety	Ignored
	16.04 LTS xenial	Fixed 229-4ubuntu19
	14.04 LTS trusty	Not affected

Notes

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.

Patch details

For informational purposes only. We recommend not to cherry-pick updates. How can I get the fixes?

Package	Patch details
systemd	Upstream: a924f43

Severity score breakdown

Parameter	Value
Base score	7.5 · High
Attack vector	Network
Attack complexity	Low
Privileges required	None
User interaction	None
Scope	Unchanged
Confidentiality	None
Integrity impact	None
Availability impact	High
Vector	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H