GHSA-H6QG-7PRX-FPPR
SSRF: verify.* modules and browser.connect/browser.launch bypass the navigation and egress guards
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 2.27.0 | flyto-core · -6 d desde divulgación | |
| Divulgación | Publicada | GHSA-H6QG-7PRX-FPPR divulgada | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Impact
`BrowserDriver.goto()` applies `_guard_navigation`, the SSRF check GHSA-662f-hr85-mg6c was written about, and cloud deployments additionally install a request-level egress guard. Five modules reached the network without either:
- `verify.run`, `verify.capture` — called raw Playwright `page.goto()` on a caller-supplied `url`, bypassing `BrowserDriver.goto()`.
- `verify.visual_diff` — worse: it drives a bare `async_playwright()` browser it creates itself, so it had no egress guard in any deployment mode. Nothing stood between the caller's URL and the network.
- `browser.connect` — `ws_endpoint` was passed to `connect_over_cdp()` unchecked. CDP grants full DevTools control of whatever answers, so an internal debugging port reachable from the runner is remote code execution, not just a probe.
- `browser.launch` — `proxy` was unchecked. Every request the browser makes is routed through it, and the egress guard inspects request URLs, not where the proxy itself points.
All five are allowed by the default module policy. Targets include the cloud instance metadata endpoint.
Patches
Fixed in 2.27.0. `verify.*` validate with `enforce_outbound_url` before navigating; `browser.connect` and `browser.launch` use `enforce_outbound_service_url`, which handles the non-HTTP schemes `validate_url_ssrf` cannot parse. In `verify.visual_diff` the check runs before the Playwright import and browser launch, so a refused target costs no launch and the guard does not depend on browsers being installed.
`browser.emulate` was given the same check on re-navigation as defense in depth (GHSA-pfg2-w999-497v is the corresponding TOCTOU).
Workarounds
Deny the affected modules via `FLYTO_MODULE_DENYLIST`, or run with `DEPLOYMENT_MODE` set to a cloud value so the egress guard covers the paths that use `BrowserDriver` (this does not cover `verify.visual_diff`).
Note on how this was found
Not reported. Found by a registry-wide audit that now runs as a test (`tests/core/test_outbound_guard_coverage.py`).
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
pypiflyto-core |
Corregida | 2.27.0 | -6 d | 2.41.0 no afectada |
2.27.0Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/flytohub/flyto-core/security/advisories/GHSA-h6qg-7prx-fpprLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
