# CVE-2024-47079: Unauthorized usage of remote hardware module because of missing channel verification

> Attackers can send unauthorized control messages to remote hardware modules due to missing channel verification in Meshtastic firmware.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2024
- **Updated:** 7 Oct 2024
- **Also known as:** UBUNTU-CVE-2024-47079

## What is CVE-2024-47079?

CVE-2024-47079 is a medium-severity missing authorization vulnerability in meshtastic firmware, published on 7 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Meshtastic is an open source, off-grid, decentralized, mesh network built to run on affordable, low-power devices. Meshtastic firmware is an open source firmware implementation for the broader project. The remote hardware module of the firmware does not have proper checks to ensure a remote hardware control message was received should be considered valid. This issue has been addressed in release version 2.5.1. All users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2024-47079?

It affects 1 product.


Products: Meshtastic Meshtastic Firmware.

## How do I fix CVE-2024-47079?

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

## Is CVE-2024-47079 being exploited?

There is no known exploitation of CVE-2024-47079 in the wild and no public exploit code.

## Other vulnerabilities in meshtastic firmware

- [CVE-2025-52464](https://insights.sbomify.com/CVE-2025-52464/): Meshtastic Repeated Public and Private Keypairs (critical 9.5)
- [CVE-2025-55293](https://insights.sbomify.com/CVE-2025-55293/): Meshtastic allows crafting of specific NodeInfo packets that overwrite any publicKey saved in the NodeDB (critical 9.4)
- [CVE-2025-24797](https://insights.sbomify.com/CVE-2025-24797/): Meshtastic incorrectly hands malformed packets leads to controlled buffer overflow (critical 9.4)
- [CVE-2025-55292](https://insights.sbomify.com/CVE-2025-55292/): In Meshtastic, an attacker can spoof licensed amateur flag for a node (high 8.2)
- [CVE-2024-47078](https://insights.sbomify.com/CVE-2024-47078/): Meshtastic firmware Authentication/Authorization Bypass via MQTT (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47079 and fix it if it is affected.

What it is: CVE-2024-47079 is a medium-severity missing authorization vulnerability in meshtastic firmware, published on 7 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47079 in the wild and no public exploit code.

Affected product: meshtastic firmware. 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-2024-47079/ (Markdown: https://insights.sbomify.com/CVE-2024-47079/index.md)
```

## Sources

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

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