Local crash via freed netlink response access
Published May 9, 2020 · Updated Aug 5, 2024
Use-after-free in iproute2 before 5.1.0 allows local users to crash the ip utility while displaying network namespaces. get_netnsid_from_name frees the netlink response buffer before rta_getattr_u32 reads NETNSA_NSID through a pointer into that freed buffer. Reachability requires local high privileges and a crafted network namespace; nondefault setuid use and C library behavior further constrain the crash path.
Summary
What happened
Use-after-free in iproute2 before 5.1.0 allows local users to crash the ip utility while displaying network namespaces. get_netnsid_from_name frees the netlink response buffer before rta_getattr_u32 reads NETNSA_NSID through a pointer into that freed buffer. Reachability requires local high privileges and a crafted network namespace; nondefault setuid use and C library behavior further constrain the crash path.
The record
- CVE
- CVE-2019-20795
- Published
- May 9, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 9, 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.
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