CVE-2017-9445
First published: Wed Jun 28 2017(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| systemd | >=223<=233 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-9445?
CVE-2017-9445 has a medium severity rating due to its potential to allow for denial of service conditions.
How do I fix CVE-2017-9445?
To fix CVE-2017-9445, update systemd to version 234 or later, which patches the vulnerability.
What causes CVE-2017-9445?
CVE-2017-9445 is caused by systemd-resolved allocating insufficient buffer sizes while processing certain crafted DNS responses.
Which versions of systemd are affected by CVE-2017-9445?
CVE-2017-9445 affects systemd versions from 223 to 233 inclusive.
Can CVE-2017-9445 be exploited remotely?
Yes, CVE-2017-9445 can be remotely exploited by a malicious DNS server sending specially crafted TCP payloads.
- agent/severity
- agent/author
- agent/references
- agent/weakness
- agent/type
- agent/event
- agent/remedy
- agent/last-modified-date
- agent/first-publish-date
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/description
- vendor/systemd project
- canonical/systemd
- version/systemd/223
- version/systemd/233