Process crash via IPv6 prefix buffer underwrite
Published May 25, 2023 · Updated Feb 13, 2025
Buffer underwrite in c-ares before 1.19.1 allows local users to crash a consuming process via a crafted IPv6 network prefix. In ares_inet_net_pton(), the IPv6 parser shortens its temporary buffer endpoint from the prefix length, then shifts more parsed bytes than fit and writes before the buffer. Internal reachability requires an administrator-supplied sort-list entry through ares_set_sortlist(); direct API consumers expose the same memory corruption to input paths they control.
Summary
What happened
Buffer underwrite in c-ares before 1.19.1 allows local users to crash a consuming process via a crafted IPv6 network prefix. In ares_inet_net_pton(), the IPv6 parser shortens its temporary buffer endpoint from the prefix length, then shifts more parsed bytes than fit and writes before the buffer. Internal reachability requires an administrator-supplied sort-list entry through ares_set_sortlist(); direct API consumers expose the same memory corruption to input paths they control.
The record
- CVE
- CVE-2023-31130
- Published
- May 25, 2023
- Updated
- Feb 13, 2025
- Vendor
- c-ares Project
- Product
- c-ares
- Classifications
- CWE-124, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 25, 2023CVE 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=< 1.19.1
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