Systemd vulnerabilitiesRanked by how likely they are to be used.
Systemd is made by Systemd Project. We track 48 published vulnerabilities in it, across 410 versions. None of them is on the list of flaws known to be exploited today. If you run Systemd, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Systemd vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Systemd's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Systemd flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 55%CVE-2017-9445High
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.
- 24%CVE-2017-15908High
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() function of the 'systemd-resolved' service...
- 15%CVE-2017-9217High
systemd-resolved through 233 allows remote attackers to cause a denial of service (daemon crash) via a crafted DNS response with an empty question section.
- 8.8%CVE-2021-33910Medium
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 by a local attacker) that results in...
- 7.4%CVE-2018-1049Medium
In systemd prior to 234 a race condition exists between .mount and .automount units such that automount requests from kernel may not be serviced by systemd resulting in kernel holding the mountpoint and any processes...
- 5.4%CVE-2013-4391High
Integer overflow in the valid_user_field function in journal/journald-native.c in systemd allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a large journal data...
- 4.3%CVE-2015-7510Critical
Stack-based buffer overflow in the getpwnam and getgrnam functions of the NSS module nss-mymachines in systemd.
- 3.9%CVE-2017-1000082Critical
systemd v233 and earlier fails to safely parse usernames starting with a numeric digit (e.g.
- 3.1%CVE-2018-21029Critical
systemd 239 through 245 accepts any certificate signed by a trusted certificate authority for DNS Over TLS.
- 3.0%CVE-2018-16865High
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 journal socket.
Running Systemd? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Systemd on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 48 published vulnerabilities listed under the name Systemd, across 410 versions.
None of Systemd's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Systemd. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.