CVE-2025-53627

{"id": "CVE-2025-53627", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-53627", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2025-12-29T16:51:54.751669Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "meshtastic", "product": "firmware", "versions": [{"status": "affected", "version": ">= 2.5, < 2.7.15"}]}]}], "published": "2025-12-29T17:15:45.287", "references": [{"url": "https://github.com/meshtastic/firmware/security/advisories/GHSA-377p-prwp-4hwf", "tags": ["Exploit", "Vendor Advisory"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-1287"}]}], "descriptions": [{"lang": "en", "value": "Meshtastic is an open source mesh networking solution. The Meshtastic firmware (starting from version 2.5) introduces asymmetric encryption (PKI) for direct messages, but when the `pki_encrypted` flag is missing, the firmware silently falls back to legacy AES-256-CTR channel encryption. This was an intentional decision to maintain backwards compatibility. However, the end-user applications, like Web app, iOS/Android app, and applications built on top of Meshtastic using the SDK, did not have a way to differentiate between end-to-end encrypted DMs and the legacy DMs. This creates a downgrade attack path where adversaries who know a shared channel key can craft and inject spoofed direct messages that are displayed as if they were PKC encrypted. Users are not given any feedback of whether a direct message was decrypted with PKI or with legacy symmetric encryption, undermining the expected security guarantees of the PKI rollout. Version 2.7.15 fixes this issue."}, {"lang": "es", "value": "Meshtastic es una soluci\u00f3n de red mallada de c\u00f3digo abierto. El firmware de Meshtastic (a partir de la versi\u00f3n 2.5) introduce cifrado asim\u00e9trico (PKI) para mensajes directos, pero cuando falta el indicador 'pki_encrypted', el firmware recurre silenciosamente al cifrado de canal AES-256-CTR heredado. Esta fue una decisi\u00f3n intencional para mantener la compatibilidad con versiones anteriores. Sin embargo, las aplicaciones de usuario final, como la aplicaci\u00f3n web, la aplicaci\u00f3n de iOS/Android y las aplicaciones construidas sobre Meshtastic usando el SDK, no ten\u00edan una forma de diferenciar entre los MD cifrados de extremo a extremo y los MD heredados. Esto crea una ruta de ataque de degradaci\u00f3n donde los adversarios que conocen una clave de canal compartida pueden elaborar e inyectar mensajes directos falsificados que se muestran como si estuvieran cifrados con PKC. Los usuarios no reciben ninguna retroalimentaci\u00f3n de si un mensaje directo fue descifrado con PKI o con cifrado sim\u00e9trico heredado, socavando las garant\u00edas de seguridad esperadas del despliegue de PKI. La versi\u00f3n 2.7.15 corrige este problema."}], "lastModified": "2026-10-07T12:10:00.170", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:meshtastic:meshtastic_firmware:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "E437EA39-C5BA-48F0-916D-3599DA4674DB", "versionEndExcluding": "2.7.15", "versionStartIncluding": "2.5.0"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}