GHSA-7J2V-G84W-M75V
Legacy GUI reads KDF settings from a CWD-relative crypt_settings.json, enabling a planted KDF downgrade
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-7J2V-G84W-M75V 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 |
crypt_settings.py defines CONFIG_FILE as the absolute per-user path ~/.crypt_settings.json (line 20) but reassigns it at line 84 to the bare relative name 'crypt_settings.json', shadowing it. The legacy Tk GUI's SettingsTab.load_settings/save_settings therefore read and write whatever file sits in the process launch directory. A crypt_settings.json planted in the CWD (e.g. sha256:1 with all memory-hard KDFs disabled) silently reduces every file encrypted in that GUI session to ~1 hash round -- the weak-KDF preflight does not fire because one hash iteration is present -- and an attacker later brute-forces the ciphertext offline.
Fix (1.4.9): the line-84 reassignment is removed so the config always resolves to the absolute per-user path, and load_settings warns when the loaded KDF configuration provides no memory-hard or iterated key stretching. Affects both the 1.4.x and 1.5.x lines. Tracked as gitlab#235.
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-7j2v-g84w-m75vLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
