https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 22:36:46 +0000 https://cve.radiocsirt.org/vuln/bdu:2017-01575 bdu:2017-01575 https://cve.radiocsirt.org/vuln/bdu:2017-01575 https://cve.radiocsirt.org/vuln/cnvd-2017-15914 cnvd-2017-15914 https://cve.radiocsirt.org/vuln/cnvd-2017-15914 https://cve.radiocsirt.org/vuln/euvd-2026-75872 EUVD-2026-75872 https://cve.radiocsirt.org/vuln/euvd-2026-75872 https://cve.radiocsirt.org/vuln/fkie_cve-2017-9445 <p>In systemd through 233, certain sizes passed to dns_packet_new in systemd-resolved can cause it to allocate a buffer that&#39;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&#39;s too small, and subsequently write arbitrary data beyond the end of it.</p> <p>In systemd through 233, certain sizes passed to dns_packet_new in systemd-resolved can cause it to allocate a buffer that&#39;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&#39;s too small, and subsequently write arbitrary data beyond the end of it.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2017-9445 https://cve.radiocsirt.org/vuln/ghsa-42xm-66qf-5jj8 <p>In systemd through 233, certain sizes passed to dns_packet_new in systemd-resolved can cause it to allocate a buffer that&#39;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&#39;s too small, and subsequently write arbitrary data beyond the end of it.</p> <p>In systemd through 233, certain sizes passed to dns_packet_new in systemd-resolved can cause it to allocate a buffer that&#39;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&#39;s too small, and subsequently write arbitrary data beyond the end of it.</p> https://cve.radiocsirt.org/vuln/ghsa-42xm-66qf-5jj8 https://cve.radiocsirt.org/vuln/gsd-2017-9445 gsd-2017-9445 https://cve.radiocsirt.org/vuln/gsd-2017-9445 https://cve.radiocsirt.org/vuln/opensuse-su-2024:11420-1 <p>libsystemd0-249.4-2.2 on GA media</p> <p>libsystemd0-249.4-2.2 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:11420-1 https://cve.radiocsirt.org/vuln/suse-su-2017:1898-1 <p>Security update for systemd, dracut</p> <p>Security update for systemd, dracut</p> https://cve.radiocsirt.org/vuln/suse-su-2017:1898-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-9445 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: systemd</p> <p>In systemd through 233, certain sizes passed to dns_packet_new in systemd-resolved can cause it to allocate a buffer that&#39;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&#39;s too small, and subsequently write arbitrary data beyond the end of it.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: systemd</p> <p>In systemd through 233, certain sizes passed to dns_packet_new in systemd-resolved can cause it to allocate a buffer that&#39;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&#39;s too small, and subsequently write arbitrary data beyond the end of it.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-9445