GHSA-PXXJ-78WV-CMF8
Unauthenticated arbitrary file write and read via testing.visual.compare diff_path/expected/actual
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-PXXJ-78WV-CMF8 divulgada | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Impact
`testing.visual.compare` accepted a caller-supplied `diff_path` and wrote the comparison's PNG output to it without confining the path to `FLYTO_SANDBOX_DIR`. The same module's `expected` and `actual` parameters read a caller-supplied local path with no confinement.
This module declares no `required_permissions` and is allowed by the default module policy, so unlike the previously reported file-write issues it needed no permission grant at all. Any caller able to run a workflow could write attacker-influenceable bytes to any path the runner process can write — `~/.ssh/authorized_keys`, a cron directory, or the application's own source — and read any file the process can read.
This is the same defect as GHSA-p64w-hgfm-824v (`browser.download` `save_path`) and GHSA-wc94-386q-5478 (unconfined reader paths), in a module those fix waves did not cover.
Patches
Fixed in 2.27.0. `diff_path` and the local-path branch of `expected`/`actual` are confined with `validate_path_with_env_config`. The `diff_path` check runs at function entry, before the Node/worker availability checks, so the boundary does not depend on an optional toolchain being installed.
Workarounds
Set `FLYTO_SANDBOX_DIR` to a directory the workflow is allowed to touch, or deny `testing.visual.compare` via `FLYTO_MODULE_DENYLIST`.
Note on how this was found
Not reported. Found by a registry-wide audit that now runs as a test (`tests/core/test_write_sink_coverage.py`): every module declaring a path-shaped parameter must reach the sandbox helper, or carry a written exemption. See SECURITY_STATUS.md.
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-pxxj-78wv-cmf8Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
