GHSA-Q8P3-7H6H-GHFR
Identity.load trusts the stored fingerprint without re-deriving it, enabling silent key substitution
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-Q8P3-7H6H-GHFR divulgada | |
| Remediación | Parche 1.4.9 | openssl-encrypt · 1 d desde divulgación | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Identity.load reads the `fingerprint` field verbatim from an identity's `identity.json` and never re-derives it from the actual public-key `.pem` files, unlike the import path (import_public), which calls check_fingerprint_consistency() and fails closed.
Under the supplied-store threat model (a shared contacts directory, an extracted archive, --identity-store pointing at attacker-controlled files), a store whose identity.json claims a genuine out-of-band-verified fingerprint but whose .pem files hold ATTACKER keys is indistinguishable from a real pinned contact:
- `identity show` prints the good (claimed) fingerprint while `encrypt --for-identity` encapsulates the file to the attacker's ML-KEM key (F6);
- `decrypt_file_asymmetric` verifies the ML-DSA signature against the substituted signing_public.pem and prints "Signature verified from: <legitimate fingerprint>", so a forged file passes the only authenticity check the format has (F7);
- re-importing the real bundle raises no TOFU warning, because add_identity compared the JSON-claimed fingerprint rather than one recomputed from the keys.
Fix (1.4.9): Identity.load now calls check_fingerprint_consistency() and fails closed when the stored fingerprint does not match the fingerprint recomputed from the public keys, so a substituted store entry is rejected (and skipped/reported by list_identities) instead of being used under a forged fingerprint. The add_identity TOFU key-change check now compares recomputed fingerprints on both sides, so a key substitution is detected from the actual keys. Affects both the 1.4.x and 1.5.x lines. Tracked as gitlab#230.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
pypiopenssl-encrypt |
Corregida | 1.4.9 | 1 d | 1.4.9 no afectada |
1.4.9Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-q8p3-7h6h-ghfrLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
