Impact
Meshtastic firmware before 2.7 advertising a User.long_name containing a malformed UTF‑8 sequence to corrupt the on‑device node database. The corrupted entry triggers a validation failure in the iOS app’s BLE sync routine, forcing the device into a fail‑retry loop and effectively stripping iOS the poisoned entry expires or is removed. The flaw is not limited to specially crafted payloads; ordinary buffer truncation can produce the same corruption. Recognized as CWE‑20, the weakness arises from insufficient input validation when storing broadcast data.
Affected Systems
The vulnerability affects Meshtastic firmware releases prior to version 2.7.23.b246bcd. Devices running those firmware versions on any platform that connects via the iOS app (and potentially other BLE‑based managers) are impacted. The issue is tied to the User.long_name field broadcast over LoRa.
Risk and Exploitability
The CVSS score of 7.5 indicates a high‑severity denial‑of‑service condition. The EPSS score is < 1 %, suggesting that exploitation is unexpectedly rare, and the vulnerability is not listed in the CISA KEV catalog. Attackers would need to be part of the mesh to inject a malformed name, meaning the attack vector is material broadcast over LoRa. Once the forged node joins the mesh, its poisoned entry propagates through any node that caches the database, extending the outage across the entire network until the stale data ages out or is repaired.
OpenCVE Enrichment