Stack corruption via unchecked TCP flag parsing
Published Aug 31, 2022 · Updated Sep 16, 2024
Out-of-bounds write in Zephyr RTOS 3.0 and earlier allows remote attackers to corrupt stack data via a malformed TCP packet. In subsys/net/ip/tcp.c, tcp_flags parses th_flags without validating ECN- or CWR-only input, leaves len at zero, then writes a null byte to buf[-1]. No authentication or user interaction is required; the disclosed consequence is alteration of adjacent stack data, not code execution.
Summary
What happened
Out-of-bounds write in Zephyr RTOS 3.0 and earlier allows remote attackers to corrupt stack data via a malformed TCP packet. In subsys/net/ip/tcp.c, tcp_flags parses th_flags without validating ECN- or CWR-only input, leaves len at zero, then writes a null byte to buf[-1]. No authentication or user interaction is required; the disclosed consequence is alteration of adjacent stack data, not code execution.
The record
- CVE
- CVE-2022-1841
- Published
- Aug 31, 2022
- Updated
- Sep 16, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 31, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=v3.0
What conditions does exploitation require?
What is affected?
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