Lucene search

K
ubuntucveUbuntu.comUB:CVE-2017-9445
HistoryJun 27, 2017 - 12:00 a.m.

CVE-2017-9445

2017-06-2700:00:00
ubuntu.com
ubuntu.com
6

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.528 Medium

EPSS

Percentile

97.6%

In systemd through 233, certain sizes passed to dns_packet_new in
systemd-resolved can cause it to allocate a buffer that’s too small. A
malicious DNS server can exploit this via a response with a specially
crafted TCP payload to trick systemd-resolved into allocating a buffer
that’s too small, and subsequently write arbitrary data beyond the end of
it.

Bugs

Notes

Author Note
chrisccoulson I believe this was introduced in v223 by https://github.com/systemd/systemd/commit/a0166609f782da91710dea9183d1bf138538db37 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.
OSVersionArchitecturePackageVersionFilename
ubuntu16.04noarchsystemd< 229-4ubuntu19UNKNOWN
ubuntu16.10noarchsystemd< 231-9ubuntu5UNKNOWN
ubuntu17.04noarchsystemd< 232-21ubuntu5UNKNOWN

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.528 Medium

EPSS

Percentile

97.6%