published 28 Jun 2017 · updated 5 Aug 2024
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
6.0MediumEPSS 59%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 59%. No fixed version is recorded.
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.
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket