GHSA-CVH3-HF56-G9XM
Remote project and task metadata is injected into the coding agent's prompt
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-CVH3-HF56-G9XM divulgada · CVSS 3.7 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Affects all veans versions (veans has no tagged release yet).
## Summary
A project member with write access sets a project title, or task titles and descriptions, that veans feeds verbatim into a coding agent's instructions on every session start. The text is rendered inside the authoritative instruction block, so the agent may follow it.
## Details
- `veans/internal/commands/prompt.tmpl:1-8` and `veans/internal/commands/prime.go:87-97` render the fields inside the authority block.
- The hook runs `prime` on SessionStart and PreCompact (`veans/internal/bootstrap/hooks.go:35,41`).
- Three of the four rendered fields come from `.veans.yml`, which adds nothing because the repo already controls CLAUDE.md. `ProjectTitle` (from the server) and task content from `list`/`show` are the real boundary.
- On an untrusted server (see the `VEANS_TOKEN` redirect advisory), the server itself controls all of this content.
## Impact
Prompt injection into an agent that can read and change the developer's checkout and run commands. Requires write access to the project (or a hostile server), and depends on the agent acting on the injected text.
## Fix
Two parts.
1. Trust gate: an untrusted server's metadata never reaches the prompt, because `prime` fails closed when it isn't interactive. It renders without remote metadata, plus a hint to run any veans command interactively to trust the server.
2. Fencing, which is still required: a writer on a *trusted* server can set `ProjectTitle` and task content. Render remote metadata and task content as a fenced, labeled untrusted-data block, outside the authority section.
The trust gate is a single origin check in the client/runtime setup (`veans/internal/commands/runtime.go:57-63`), with trust records in global XDG state keyed by normalized origin plus repo identity, an interactive confirmation, and fail-closed behavior when non-interactive.
_Found via internal security review (csf #3, 03 #13, deep #9)._
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Gocode.vikunja.io/veans |
Sin parche | — | — | — |
Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-cvh3-hf56-g9xmLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
