Message spoofing via unchecked MQTT packet provenance
Published Feb 18, 2025 · Updated Feb 19, 2025
Message spoofing in Meshtastic Firmware 2.5.0 through 2.5.18 allows remote attackers to inject forged direct messages over MQTT. The MQTT packet-handling path forwards crafted packets into direct-message clients without confirming that PKC decoded them. MQTT ingestion must be enabled and a recipient must view the message; the reported impact is false message attribution, not code execution or disclosure.
Summary
What happened
Message spoofing in Meshtastic Firmware 2.5.0 through 2.5.18 allows remote attackers to inject forged direct messages over MQTT. The MQTT packet-handling path forwards crafted packets into direct-message clients without confirming that PKC decoded them. MQTT ingestion must be enabled and a recipient must view the message; the reported impact is false message attribution, not code execution or disclosure.
The record
- CVE
- CVE-2025-21608
- Published
- Feb 18, 2025
- Updated
- Feb 19, 2025
- Vendor
- Meshtastic
- Product
- Meshtastic Firmware
- Classifications
- CWE-668, T1565.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 2025CVE publishedPublication date reported by the CVE source.
- Feb 19, 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.0, <= 2.5.18
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
No public exploit references are available in this record.
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