Denial of Service

Every one of the 7 is a mark on the map. Named now: 1 to 7, most at risk first.

1. In systemd 223 through 235, a remote DNS server can respond with a custom crafted DNS NSEC resource record to trigger an infinite loop in the dns_packet_read_type_window() functio…CVE-2017-15908Systemd Project · 24% likely

   CWE-835

2. basic/unit-name.c in systemd prior to 246.15, 247.8, 248.5, and 249.1 has a Memory Allocation with an Excessive Size Value (involving strdupa and alloca for a pathname controlled…CVE-2021-33910Systemd Project · CVSS 5.5 · 8.8% likely

   CWE-770

3. An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when many entries are sent to the jo…CVE-2018-16865The systemd Project · CVSS 7.5 · 3.0% likely

   CWE-770

4. An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when a program with long command lin…CVE-2018-16864The systemd Project · CVSS 7.4 · 0.7% likely

   CWE-770

5. An issue was discovered in button_open in login/logind-button.c in systemd before 243. When executing the udevadm trigger command, a memory leak may occur.CVE-2019-20386Systemd Project · CVSS 5.1 · 0.4% likely

   CWE-401

6. A memory leak was discovered in the backport of fixes for CVE-2018-16864 in Red Hat Enterprise Linux. Function dispatch_message_real() in journald-server.c does not free the memor…CVE-2019-3815The systemd Project · CVSS 3.3 · 0.4% likely

   CWE-401

7. systemd 250 and 251 allows local users to achieve a systemd-coredump deadlock by triggering a crash that has a long backtrace. This occurs in parse_elf_object in shared/elf-util.c…CVE-2022-45873Systemd Project · CVSS 5.5 · 0.3% likely

   CWE-400

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.