Unauthenticated memory corruption via inconsistent IPv6 lengths
Published Jun 17, 2020 · Updated Aug 4, 2024
Out-of-bounds write in the Treck TCP/IP stack before 5.0.1.35 allows remote attackers to corrupt memory using malformed IPv6 packets. The IPv6 component mishandles inconsistent packet-length parameters across a sequence of malformed packets and writes beyond the intended buffer. Any network path that delivers IPv6 traffic to an embedded device using the affected stack is sufficient; the documented consequence is memory corruption, without a product-specific execution outcome.
Summary
What happened
Out-of-bounds write in the Treck TCP/IP stack before 5.0.1.35 allows remote attackers to corrupt memory using malformed IPv6 packets. The IPv6 component mishandles inconsistent packet-length parameters across a sequence of malformed packets and writes beyond the intended buffer. Any network path that delivers IPv6 traffic to an embedded device using the affected stack is sufficient; the documented consequence is memory corruption, without a product-specific execution outcome.
The record
- CVE
- CVE-2020-11897
- Published
- Jun 17, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- 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.
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