CVE-2017-9445

Published: 27 June 2017

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.

Priority

CVSS 3 base score: 7.5

Status

Package	Release	Status
systemd Launchpad, Ubuntu, Debian	Upstream	Needed




	Ubuntu 16.04 LTS (Xenial Xerus)	Released (229-4ubuntu19)
	Ubuntu 14.04 ESM (Trusty Tahr)	Not vulnerable (204-5ubuntu20.24)

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.

References

Bugs

https://launchpad.net/bugs/1695546

Join the discussion

Canonical is offering Extended Security Maintenance

Canonical is offering Ubuntu 14.04 Extended Security Maintenance (ESM) for security fixes and essential packages.

Find out more about ESM