DNS service crash via null token array
Published Jun 6, 2024 · Updated Feb 13, 2025
NULL-pointer dereference in robdns commit d76d2e6 allows remote attackers to crash the DNS service through crafted input. conf-parse.c takes an address within item->tokens without first checking whether the token array is null, invoking undefined behavior. No authentication or user interaction is required, but the public record does not identify the exact network input path that reaches this parser.
Summary
What happened
NULL-pointer dereference in robdns commit d76d2e6 allows remote attackers to crash the DNS service through crafted input. conf-parse.c takes an address within item->tokens without first checking whether the token array is null, invoking undefined behavior. No authentication or user interaction is required, but the public record does not identify the exact network input path that reaches this parser.
The record
- CVE
- CVE-2024-24194
- Published
- Jun 6, 2024
- Updated
- Feb 13, 2025
- Vendor
- Robert Graham
- Product
- robdns
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 6, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=d76d2e6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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