7.5 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
NONE
Integrity Impact
NONE
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
5 Medium
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
NONE
Integrity Impact
NONE
Availability Impact
PARTIAL
AV:N/AC:L/Au:N/C:N/I:N/A:P
0.007 Low
EPSS
Percentile
80.1%
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.
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. |
7.5 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
NONE
Integrity Impact
NONE
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
5 Medium
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
NONE
Integrity Impact
NONE
Availability Impact
PARTIAL
AV:N/AC:L/Au:N/C:N/I:N/A:P
0.007 Low
EPSS
Percentile
80.1%