# CVE-2022-39274: Buffer Overflow in `ProcessRadioRxDone` in LoRaMac-node

> An attacker can trigger a buffer overflow in LoRaMac-node via crafted radio frames, potentially leading to remote code execution or denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-7vv8-73pc-63c2

## What is CVE-2022-39274?

CVE-2022-39274 is a high-severity memory corruption vulnerability in Lora-net LoRaMac-node, published on 6 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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`.

Weakness: CWE-193 (Off-by-one Error), CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2022-39274?

It affects 1 product.


Products: Semtech Loramac-Node.

## How do I fix CVE-2022-39274?

No fix has been published for CVE-2022-39274 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-39274 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39274 exists.

## Other vulnerabilities in Lora-net LoRaMac-node

- [CVE-2020-11068](https://insights.sbomify.com/CVE-2020-11068/): Potential Buffer Overflow in LoRaMac-node (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39274 and fix it if it is affected.

What it is: CVE-2022-39274 is a high-severity memory corruption vulnerability in Lora-net LoRaMac-node, published on 6 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39274 exists.

Affected product: Lora-net LoRaMac-node. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-39274/ (Markdown: https://insights.sbomify.com/CVE-2022-39274/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-39274
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-39274
- OSV: https://osv.dev/vulnerability/CVE-2022-39274

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-39274/
Summaries are generated and may contain mistakes; the official description above is the record.