Device crash or code execution via length underflow
Published Oct 6, 2022 · Updated Apr 22, 2025
Buffer overflow in LoRaMac-node before 4.7.0 allows remote authenticated users to crash an end device or execute code via radio frames. ProcessRadioRxDone reads a header byte from an empty reused payload, then subtracts one from the zero length and copies 65,280 bytes into a 255-byte receive buffer. The gate is a crafted proprietary frame plus low-privilege network access; resulting corruption crashes the node or leaves its data segment attacker-controlled.
Summary
What happened
Buffer overflow in LoRaMac-node before 4.7.0 allows remote authenticated users to crash an end device or execute code via radio frames. ProcessRadioRxDone reads a header byte from an empty reused payload, then subtracts one from the zero length and copies 65,280 bytes into a 255-byte receive buffer. The gate is a crafted proprietary frame plus low-privilege network access; resulting corruption crashes the node or leaves its data segment attacker-controlled.
The record
- CVE
- CVE-2022-39274
- Published
- Oct 6, 2022
- Updated
- Apr 22, 2025
- Vendor
- Semtech
- Product
- LoRaMac-node
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 6, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.7.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
- Empty proprietary-frame proof of conceptproof of concept · demonstrated
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