Code execution via premature nameserver response pointer corruption
Published Jun 18, 2020 · Updated Aug 5, 2024
Pointer corruption in GNU adns before 1.5.2 allows remote attackers controlling the local recursive resolver to execute application code. When a nameserver responds before adns issues its query, the reply path applies the wrong number of pointer dereferences and corrupts a pointer. The attacker must control the configured recursive resolver; successful exploitation runs code with the privileges of an application calling adns.
Summary
What happened
Pointer corruption in GNU adns before 1.5.2 allows remote attackers controlling the local recursive resolver to execute application code. When a nameserver responds before adns issues its query, the reply path applies the wrong number of pointer dereferences and corrupts a pointer. The attacker must control the configured recursive resolver; successful exploitation runs code with the privileges of an application calling adns.
The record
- CVE
- CVE-2017-9105
- Published
- Jun 18, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1203
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 18, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo