GHSA-GRHJ-CPMG-F5MX
Recovery-slot presence was not authenticated; recovery slots could be stripped from an envelope file undetected
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-GRHJ-CPMG-F5MX 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 |
Envelope-format encrypted files wrap a random data key (DEK) under a password key (encryption.wrapped_dek) and, optionally, under recovery credentials (encryption.dek_slots, authenticated by a DEK-keyed encryption.dek_slots_mac). The recovery-slot fields were excluded from the bulk AEAD associated data so slots could be added or removed without re-encrypting the payload, and the slot-set MAC was only verified when slots were present. As a result, an attacker who could modify the file header could delete the recovery-slot fields wholesale -- no key required -- and the password decryption path would proceed as if the file had never had any recovery slots. A recovery path the owner deliberately added could be silently removed (CWE-354 / CWE-347).
Fix (1.4.9, both lines): a recovery-slot-count commitment (encryption.dek_slot_count) is bound into the wrapped DEK's AEAD associated data. Because the wrapped DEK cannot be recomputed without the password key, and decryption binds the count deterministically (with no legacy fallback for files that carry the commitment), the recovery slots can no longer be stripped, the count zeroed, or the file downgraded without the password unwrap failing closed; decryption also fails closed unless the present slot set matches the authenticated count. Note: managing recovery slots (add/remove) now requires the primary password, since re-binding the wrapped key to the new count needs the password key -- a recovery credential alone no longer suffices. Tracked as gitlab#264.
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-grhj-cpmg-f5mxLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
