Node location disclosure via unthrottled traceroute responses
Published Jul 11, 2025 · Updated Jul 11, 2025
Improper interaction throttling in Meshtastic Firmware before 2.5.1 allows remote attackers to expose node location via traceroute. The remote node's Traceroute_APP request path returns a radio response for every accepted request without tracking or limiting request frequency. An attacker sharing the target's AES key and LoRa radio parameters can collect rapid SNR samples to infer position and can generate 2:1 reflected mesh traffic.
Summary
What happened
Improper interaction throttling in Meshtastic Firmware before 2.5.1 allows remote attackers to expose node location via traceroute. The remote node's Traceroute_APP request path returns a radio response for every accepted request without tracking or limiting request frequency. An attacker sharing the target's AES key and LoRa radio parameters can collect rapid SNR samples to infer position and can generate 2:1 reflected mesh traffic.
The record
- CVE
- CVE-2024-47065
- Published
- Jul 11, 2025
- Updated
- Jul 11, 2025
- Vendor
- Meshtastic
- Product
- Meshtastic Firmware
- Classifications
- CWE-799, T1498.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 11, 2025CVE publishedPublication date reported by the CVE source.
- Jul 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Repeated traceroute request procedureproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo