Service interruption via unchecked UDP packet length
Published May 13, 2021 · Updated Sep 16, 2024
Memory-boundary flaw in Hilscher rcX RTOS before 2.1.14.1 allows remote attackers to interrupt devices via crafted UDP packets. The UDP receive path trusts the length declared in a packet without checking it against the datagram's actual length, allowing processing beyond the received buffer. No authentication or user interaction is required; a crafted network packet can interrupt the embedded device, while published impact is limited to availability.
Summary
What happened
Memory-boundary flaw in Hilscher rcX RTOS before 2.1.14.1 allows remote attackers to interrupt devices via crafted UDP packets. The UDP receive path trusts the length declared in a packet without checking it against the datagram's actual length, allowing processing beyond the received buffer. No authentication or user interaction is required; a crafted network packet can interrupt the embedded device, while published impact is limited to availability.
The record
- CVE
- CVE-2021-20988
- Published
- May 13, 2021
- Updated
- Sep 16, 2024
- Vendor
- Hilscher
- Product
- rcX RTOS
- Classifications
- CWE-119, T1498
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 2021CVE 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 <V2.1.14.1
What conditions does exploitation require?
What is affected?
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