Critical Meshtastic Vulnerability Allows Attackers to Read Encrypted Messages

A critical security vulnerability has been discovered in Meshtastic, the popular open-source mesh networking platform, that could allow attackers to decrypt private direct messages and compromise remote administration features.

The vulnerability, tracked as GHSA-gq7v-jr8c-mfr7, affects all versions above 2.5.0 and stems from duplicated cryptographic keys and inadequate randomness during key generation processes.

The security vulnerability was initially discovered when researchers found that hardware vendors’ flashing procedures were inadvertently creating identical public and private key pairs across multiple devices.

This vendor cloning issue meant that different Meshtastic devices could end up with the same cryptographic credentials, fundamentally undermining the security model of the mesh network.

During the investigation, security researchers uncovered a deeper problem with the platform’s cryptographic implementation.

The Meshtastic firmware’s usage of the rweather/crypto library was failing to properly initialize the internal randomness pool on certain hardware platforms.

This initialization failure resulted in low-entropy key generation, where cryptographic keys lacked sufficient randomness to ensure uniqueness and security.

The combination of vendor cloning and inadequate entropy created a perfect storm for widespread key compromise across the Meshtastic ecosystem.

Meshtastic Vulnerability

The impact of this vulnerability extends to two critical areas of Meshtastic functionality. When users with compromised key pairs send direct messages through the mesh network, those communications become vulnerable to interception and decryption by attackers who have compiled lists of the duplicated keys.

This represents a significant privacy breach for users who believed their direct communications were secure.

The remote administration feature faces even more complex security implications. In scenarios where a compromised key is added as a remote administrator, any individual with access to that private key could gain administrative control over mesh nodes.

The situation becomes more sophisticated when the remotely administered node itself possesses the compromised key pair.

In such cases, an attacker would need to determine the public key of an authorized administrator, then use the compromised private key to generate the resulting shared key, effectively impersonating the legitimate administrator to send unauthorized commands to remote nodes.

Immediate Patches

Meshtastic has responded swiftly to address these vulnerabilities with the release of version 2.6.11, which implements several critical security improvements.

The updated firmware now warns users when compromised keys are detected on their devices and delays key generation until users set their LoRa region for the first time, effectively eliminating the vendor cloning issue.

Additionally, the patch introduces multiple sources of randomness to improve the rweather/crypto library’s random number generation initialization process.

A future release, version 2.6.12, will automatically detect and wipe known compromised keys when discovered on devices.

For immediate protection, users can perform a complete device wipe using the Python Command Line Interface with the command “meshtastic –factory-reset-device.”

However, users requiring truly high-entropy keys can generate them manually using OpenSSL: “openssl genpkey -algorithm x25519 -outform DER | tail -c32 | base64.”

The vulnerability disclosure highlights the importance of proper cryptographic implementation in IoT mesh networking devices and demonstrates how manufacturing processes can inadvertently compromise security across entire device populations.

Find this Story Interesting! Follow us on LinkedIn and X to Get More Instant Updates.