GHSA-2592-7M3G-7FQ6
Integrity proxy trusts entire RFC 1918 private address space by default
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-2592-7M3G-7FQ6 divulgada | |
| Remediación | Parche 1.4.0 | openssl_encrypt · 21 d desde divulgación | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Severity: HIGH
Summary
The `IntegrityProxyConfig` in `openssl_encrypt_server/config.py` at lines 86-97 defaults `trusted_proxies` to include `10.0.0.0/8`, `172.16.0.0/12`, and `192.168.0.0/16` — the entire RFC 1918 private address space.
Affected Code
class IntegrityProxyConfig(BaseSettings):
trusted_proxies: List[str] = [
"127.0.0.1", "::1",
"10.0.0.0/8", # Entire class A private
"172.16.0.0/12", # Entire class B private
"192.168.0.0/16" # Entire class C private
]While `ProxyAuth` validation (line 84) rejects networks with prefix < 24, this validation could be changed or bypassed. The Pepper module correctly defaults to only localhost.
Impact
If ProxyAuth validation is relaxed, any host on a private network could forge client certificate headers, bypassing mTLS authentication entirely.
Recommended Fix
- Default to localhost only (`127.0.0.1`, `::1`) like the Pepper module
- Require explicit configuration for broader trust ranges
Fix
Fixed in commit `7462ad0` on branch `releases/1.4.x` — changed default trusted_proxies from all RFC 1918 ranges to localhost only (["127.0.0.1", "::1"]).
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
pypiopenssl_encrypt |
Corregida | 1.4.0 | 21 d | 1.4.9 no afectada |
1.4.0Arsenal 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-2592-7m3g-7fq6Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
