CVE-2022-39274
Summary
| CVE | CVE-2022-39274 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2022-10-06 18:16:00 UTC |
| Updated | 2023-06-27 18:44:00 UTC |
| Description | LoRaMac-node is a reference implementation and documentation of a LoRa network node. Versions of LoRaMac-node prior to 4.7.0 are vulnerable to a buffer overflow. Improper size validation of the incoming radio frames can lead to an 65280-byte out-of-bounds write. The function `ProcessRadioRxDone` implicitly expects incoming radio frames to have at least a payload of one byte or more. An empty payload leads to a 1-byte out-of-bounds read of user controlled content when the payload buffer is reused. This allows an attacker to craft a FRAME_TYPE_PROPRIETARY frame with size -1 which results in an 65280-byte out-of-bounds memcopy likely with partially controlled attacker data. Corrupting a large part if the data section is likely to cause a DoS. If the large out-of-bounds write does not immediately crash the attacker may gain control over the execution due to now controlling large parts of the data section. Users are advised to upgrade either by updating their package or by manually applying the patch commit `e851b079`. |
Risk And Classification
Problem Types: CWE-193
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Semtech | Loramac-node | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/Lora-net/LoRaMac-node/releases/tag/v4.7.0 | MISC | github.com | |
| cve-website | MISC | www.cve.org | |
| Fixed potential buffer overflow in `ProcessRadioRxDone` · Lora-net/LoRaMac-node@e851b07 · GitHub | MISC | github.com | |
| Buffer Overflow in `ProcessRadioRxDone` · Advisory · Lora-net/LoRaMac-node · GitHub | CONFIRM | github.com | |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.