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.
Notes
Author | Note |
---|---|
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. |
Priority
Status
Package | Release | Status |
---|---|---|
systemd Launchpad, Ubuntu, Debian |
trusty |
Not vulnerable
(204-5ubuntu20.24)
|
upstream |
Needed
|
|
xenial |
Released
(229-4ubuntu19)
|
|
yakkety |
Ignored
(end of life)
|
|
zesty |
Released
(232-21ubuntu4)
|
|
Patches: upstream: https://github.com/systemd/systemd/commit/a924f43f30f9c4acaf70618dd2a055f8b0f166be |
Severity score breakdown
Parameter | Value |
---|---|
Base score | 7.5 |
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 |