Memory corruption via allocation integer overflow
Published Jun 17, 2020 · Updated Sep 30, 2025
Integer overflow in the Treck TCP/IP stack before 6.0.1.66 allows remote attackers to corrupt memory with crafted network packets. The memory-allocation path calculates an incorrect size, obtains an undersized buffer, and then writes data beyond that allocation. Network access is sufficient, with no authentication or user interaction required; the bounded result is corruption of adjacent memory.
Summary
What happened
Integer overflow in the Treck TCP/IP stack before 6.0.1.66 allows remote attackers to corrupt memory with crafted network packets. The memory-allocation path calculates an incorrect size, obtains an undersized buffer, and then writes data beyond that allocation. Network access is sufficient, with no authentication or user interaction required; the bounded result is corruption of adjacent memory.
The record
- CVE
- CVE-2020-11904
- Published
- Jun 17, 2020
- Updated
- Sep 30, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2020CVE publishedPublication date reported by the CVE source.
- Sep 30, 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?
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.
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