CVE-2017-9217
published 2017-05-24CVE-2017-9217: 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.
PriorityP340high7.5CVSS 3.1
AVNACLPRNUINSUCNINAH
EPSS
15.42%
96.4th percentile
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.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | systemd | < systemd 232-24 (bookworm) | systemd 232-24 (bookworm) |
| systemd_project | systemd | <= 233 | — |
| systemd_project | systemd | >= 0 < 232-24 | 232-24 |
| systemd_project | systemd | >= 0 < 232-24 | 232-24 |
| systemd_project | systemd | >= 0 < 232-24 | 232-24 |
| systemd_project | systemd | >= 0 < 232-24 | 232-24 |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:N/A:P
osv7.5HIGH
vendor_debian7.5HIGH
vendor_redhat7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-pv82-vf69-rqqm: systemd-resolved through 233 allows remote attackers to cause a denial of service (daemon crash) via a crafted DNS response with an empty question sec
ghsa_unreviewed·2022-05-13
CVE-2017-9217 [HIGH] CWE-476 GHSA-pv82-vf69-rqqm: systemd-resolved through 233 allows remote attackers to cause a denial of service (daemon crash) via a crafted DNS response with an empty question sec
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.
OSV
CVE-2017-9217: systemd-resolved through 233 allows remote attackers to cause a denial of service (daemon crash) via a crafted DNS response with an empty question sec
osv·2017-05-24·CVSS 7.5
CVE-2017-9217 [HIGH] CVE-2017-9217: systemd-resolved through 233 allows remote attackers to cause a denial of service (daemon crash) via a crafted DNS response with an empty question sec
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.
Red Hat
systemd: Null pointer dereference in dns_packet_is_reply_for function
vendor_redhat·2017-05-20·CVSS 7.5
CVE-2017-9217 [HIGH] CWE-476 systemd: Null pointer dereference in dns_packet_is_reply_for function
systemd: Null pointer dereference in dns_packet_is_reply_for function
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.
Statement: This issue did not affect the versions of systemd as shipped with Red Hat Enterprise Linux 7.
Package: systemd (Red Hat Enterprise Linux 7) - Not affected
Debian
CVE-2017-9217: systemd - systemd-resolved through 233 allows remote attackers to cause a denial of servic...
vendor_debian·2017·CVSS 7.5
CVE-2017-9217 [HIGH] CVE-2017-9217: systemd - systemd-resolved through 233 allows remote attackers to cause a denial of servic...
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.
Scope: local
bookworm: resolved (fixed in 232-24)
bullseye: resolved (fixed in 232-24)
forky: resolved (fixed in 232-24)
sid: resolved (fixed in 232-24)
trixie: resolved (fixed in 232-24)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2017-9217 systemd: Null pointer dereference in dns_packet_is_reply_for function
bugzilla·2017-05-25·CVSS 7.5
CVE-2017-9217 [HIGH] CVE-2017-9217 systemd: Null pointer dereference in dns_packet_is_reply_for function
CVE-2017-9217 systemd: Null pointer dereference in dns_packet_is_reply_for function
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.
Upstream bug:
https://github.com/systemd/systemd/pull/5998
Upstream patch:
https://github.com/systemd/systemd/pull/6020/commits/9e74e781f176f3b930d9c202e20532f011a5d7bc
Discussion:
Created systemd tracking bugs for this issue:
Affects: fedora-all [bug 1455495]
---
Analysis:
The issue was introduced in systemd v225 by following commit:
https://github.com/systemd/systemd/commit/f52e61da047d7fc74e83f12dbbf87e0cbcc51c73
The vulnerable code (dereferencing p->question->n_keys without first asserting on p->question) was first introduced in dns_tran
Bugzilla
CVE-2017-9217 systemd: Null pointer dereference in dns_packet_is_reply_for function [fedora-all]
bugzilla·2017-05-25·CVSS 7.5
CVE-2017-9217 [HIGH] CVE-2017-9217 systemd: Null pointer dereference in dns_packet_is_reply_for function [fedora-all]
CVE-2017-9217 systemd: Null pointer dereference in dns_packet_is_reply_for function [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple
http://www.securityfocus.com/bid/98677https://github.com/systemd/systemd/commit/a924f43f30f9c4acaf70618dd2a055f8b0f166behttps://github.com/systemd/systemd/pull/5998https://launchpad.net/bugs/1621396http://www.securityfocus.com/bid/98677https://github.com/systemd/systemd/commit/a924f43f30f9c4acaf70618dd2a055f8b0f166behttps://github.com/systemd/systemd/pull/5998https://launchpad.net/bugs/1621396https://security.netapp.com/advisory/ntap-20241213-0003/
2017-05-24
Published