GHSA-X38R-8WF3-Q9HQ
GPG detached-signature verification accepts revoked and expired keys
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-X38R-8WF3-Q9HQ 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 |
gpg_runner.verify_detached -- the single primitive behind plugin signatures (ENFORCE by default), the per-package PLUGIN.manifest, and the source-integrity manifest -- decided a signature was good from a VALIDSIG/GOODSIG status line alone, never inspecting the gpg exit status or the REVKEYSIG/EXPKEYSIG/EXPSIG status lines. GnuPG emits VALIDSIG alongside REVKEYSIG for a cryptographically valid signature made by a REVOKED key (and EXPKEYSIG/EXPSIG for an expired key or signature), so an attacker holding a compromised-then-revoked signing key -- or the project key after expiry -- still got plugins accepted and executed in the host process. The expected-fingerprint check also compared the signing (possibly subkey) fingerprint rather than the primary-key fingerprint.
Fix (1.4.9): verify_detached now requires GOODSIG + VALIDSIG, treats REVKEYSIG/EXPKEYSIG/EXPSIG/ERRSIG/BADSIG and a non-zero gpg exit as failure (fail closed), and compares VALIDSIG's primary-key fingerprint for the expected-fingerprint match. Affects both the 1.4.x and 1.5.x lines. Tracked as gitlab#232.
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-x38r-8wf3-q9hqLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
