Service interruption via unchecked TCP payload length
Published Aug 19, 2021 · Updated Aug 4, 2024
Improper input validation in HCC NicheStack before 4.3 allows remote attackers to interrupt service with a malformed TCP packet. The in_tcp module's TCP checksum computation trusts an IP-header payload size that can be smaller than the header, producing an invalid TCP payload length and out-of-bounds memory access. No authentication or user interaction is required; the resulting availability failure is published without a specific hang, crash, or reboot mode, and a low-impact out-of-bounds write is also possible.
Summary
What happened
Improper input validation in HCC NicheStack before 4.3 allows remote attackers to interrupt service with a malformed TCP packet. The in_tcp module's TCP checksum computation trusts an IP-header payload size that can be smaller than the header, producing an invalid TCP payload length and out-of-bounds memory access. No authentication or user interaction is required; the resulting availability failure is published without a specific hang, crash, or reboot mode, and a low-impact out-of-bounds write is also possible.
The record
- CVE
- CVE-2020-35684
- Published
- Aug 19, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 19, 2021CVE 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