Arbitrary memory access via IPv4 tunnel double-free
Published Jun 17, 2020 · Updated Aug 4, 2024
Double free in the Treck TCP/IP stack before 6.0.1.41 allows remote attackers to read or write arbitrary memory via malicious IPv4 tunnel packets. The IPv4 tunneling component releases the same memory allocation twice while processing a crafted packet, leaving subsequent memory access unsafe. No authentication or user action is required; the corruption can expose or alter memory and can interrupt a device by forcing a reboot.
Summary
What happened
Double free in the Treck TCP/IP stack before 6.0.1.41 allows remote attackers to read or write arbitrary memory via malicious IPv4 tunnel packets. The IPv4 tunneling component releases the same memory allocation twice while processing a crafted packet, leaving subsequent memory access unsafe. No authentication or user action is required; the corruption can expose or alter memory and can interrupt a device by forcing a reboot.
The record
- CVE
- CVE-2020-11900
- Published
- Jun 17, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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