GHSA-QQFQ-G2CV-J7V3
Crafted file with an unencrypted embedded post-quantum private key decrypts under any password
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-QQFQ-G2CV-J7V3 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 |
decrypt_file adopts a post-quantum private key embedded in a file's own metadata (encryption.pqc_private_key) verbatim whenever pqc_key_encrypted is false or absent (it defaults to False). For mayo/cross/ML-KEM hybrid algorithms the bulk decryption key derives ONLY from that embedded key, so the password-derived key is never used.
An attacker can craft a self-contained file -- a v5 header naming e.g. mayo-1-hybrid, an embedded raw private key, aead_binding:false and attacker-computed content hashes -- that decrypts under ANY password the victim types, printing "integrity verified" and writing attacker-chosen plaintext. The mayo/cross variant requires no liboqs. A user checking whether their password still opens a backup gets a false positive (authentication bypass, CWE-287).
The encryptor never legitimately produces an unencrypted embedded private key -- every store-private-key path marks it key_encrypted=True -- so an unencrypted embedded key only appears in crafted or hypothetical pre-fix legacy files.
Fix (1.4.9): decrypt_file now default-denies any file whose metadata carries an embedded PQC private key that is not marked encrypted, before any key derivation runs, so no plaintext is produced. A trusted legacy file can still be read by explicitly passing allow_unencrypted_pqc_key=True. Affects both the 1.4.x and 1.5.x lines. Tracked as gitlab#229.
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-qqfq-g2cv-j7v3Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
