Meshtastic Firmware up to 2.5.0 Traceroute_APP Response improper control of interaction frequency
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Meshtastic Firmware up to 2.5.0. Affected is an unknown function of the component Traceroute_APP Response Handler. Such manipulation leads to improper control of interaction frequency. This vulnerability is uniquely identified as CVE-2024-47065. The attack can be launched remotely. No exploit exists. The affected component should be upgraded.
Details
A vulnerability, which was classified as critical, has been found in Meshtastic Firmware up to 2.5.0. Affected by this issue is an unknown part of the component Traceroute_APP Response Handler. The manipulation with an unknown input leads to a improper control of interaction frequency vulnerability. Using CWE to declare the problem leads to CWE-799. The product does not properly limit the number or frequency of interactions that it has with an actor, such as the number of incoming requests. Impacted is confidentiality, integrity, and availability. CVE summarizes:
Meshtastic is an open source mesh networking solution. Prior to 2.5.1, traceroute responses from the remote node are not rate limited. Given that there are SNR measurements attributed to each received transmission, this is a guaranteed way to get a remote station to reliably and continuously respond. You could easily get 100 samples in a short amount of time (estimated 2 minutes), whereas passively doing the same could take hours or days. There are secondary effects that non-ratelimited traceroute does also allow a 2:1 reflected DoS of the network as well, but these concerns are less than the problem with positional confidentiality (other DoS routes exist). This vulnerability is fixed in 2.5.1.
The advisory is shared for download at github.com. This vulnerability is handled as CVE-2024-47065 since 09/17/2024. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available.
Upgrading to version 2.5.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-54776). Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.8
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Improper control of interaction frequencyCWE: CWE-799 / CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Firmware 2.5.1
Timeline
09/17/2024 🔍07/11/2025 🔍
07/11/2025 🔍
08/23/2025 🔍
Sources
Product: github.comAdvisory: GHSA-4hjx-54gf-2jh7
Status: Confirmed
CVE: CVE-2024-47065 (🔍)
GCVE (CVE): GCVE-0-2024-47065
GCVE (VulDB): GCVE-100-316172
EUVD: 🔍
Entry
Created: 07/11/2025 20:31Updated: 08/23/2025 05:16
Changes: 07/11/2025 20:31 (69), 07/11/2025 21:12 (1), 08/23/2025 05:16 (13)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.