Loramac Node
Approved changes feed: RSS · Atom
cpe:2.3:a:semtech:loramac-node:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Semtech (68fd5764-ef6f-5be2-b97f-b512becede47) |
|---|---|
| Product | Loramac Node (69860b90-f064-5bd9-aa1b-aced2e6d2b7f) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/lora-net/loramac-node |
purl2cpe | 2026-06-01 10:14:56.946652 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-39274 |
vulnerable | 2026-06-08 05:47:18.512811 |
Buffer Overflow in `ProcessRadioRxDone` in LoRaMac-node
HIGH (7.5)
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`.
Published: 2022-10-06T00:00:00.000Z
Updated: 2025-04-22T17:19:43.579Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-11068 |
vulnerable | 2026-06-08 05:16:36.390137 |
Potential Buffer Overflow in LoRaMac-node
MEDIUM (5)
In LoRaMac-node before 4.4.4, a reception buffer overflow can happen due to the received buffer size not being checked. This has been fixed in 4.4.4.
Published: 2020-06-23T16:40:12.000Z
Updated: 2024-08-04T11:21:14.647Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.