GHSA-F6MW-65V7-MCCG
Arbitrary file read via unconfined file_path/ruleset_path in data.xml.parse and verify.spec
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-F6MW-65V7-MCCG divulgada | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Impact
GHSA-wc94-386q-5478 confined the caller-supplied read paths in `data.csv.read`, `data.yaml.parse`, `excel.read`, `pdf.parse` and `image.ocr`. Two sibling modules with the same sink were missed:
- `data.xml.parse` — `file_path` was passed to `ElementTree.parse` unconfined, and the parsed document is returned to the caller. Arbitrary file read.
- `verify.spec` — `ruleset_path` was loaded unconfined. Beyond reading the file, a ruleset determines which modules the verification run executes, so an unconfined path also lets a caller load a ruleset the operator never authored.
Both declare no `required_permissions` and are allowed by the default module policy, so no grant was needed.
Patches
Fixed in 2.27.0. Both paths are confined with `validate_path_with_env_config`. In `data.xml.parse` the check was placed outside the surrounding `try`, so a rejected path surfaces as a sandbox violation rather than being flattened into a parse error.
Workarounds
Set `FLYTO_SANDBOX_DIR`, or deny `data.xml.parse` / `verify.spec` via `FLYTO_MODULE_DENYLIST`.
Related hardening in the same release
The same audit confined read paths in modules that are not reachable under the default policy and therefore need an operator grant to exploit: `browser.upload` and `aws.s3.upload` (file contents shipped to a visited page or a caller-chosen bucket), `ssh.sftp_upload`, `git.diff`, `file.exists`, and the write/delete side in `file.delete`, `git.clone`, `git.commit`, `ssh.sftp_download` and `llm.code_fix` (whose previous `'..'` substring check never blocked an absolute path).
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
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-f6mw-65v7-mccgLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
