GHSA-M29V-3G7G-9C63
Mareforma: search_claims skips verify-on-read, serving forged rows
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-M29V-3G7G-9C63 divulgada | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
What's wrong
`search_claims` never calls `_row_verified_on_read`. Its row loop applies only the PRELIMINARY-unenrolled filter, then appends the row. `query_claims` runs the same projection but additionally re-verifies REPLICATED/ESTABLISHED signatures on read (line 4023) and drops any row that fails, per the documented tamper guarantee in the comment block above it: a high-trust row whose signature does not verify is excluded from query results entirely.
So a tampered or forged high-trust row splits the two read paths. Any process with DB write access, or an attacker copying a genuine validation envelope onto a fresh row, can flip a row to ESTABLISHED. `query()` drops it; `search()` serves it at its persisted trust level. Verified in a runtime check against a forged ESTABLISHED row:
query() returns forged row: False
search() returns forged row: True # support_level ESTABLISHED, 'verified' key absentThe docstring makes this worse: `search_claims` promises "the same projection as query_claims" and that the `include_unverified` filter "applies identically", so callers reasonably trust search results equally. The forged row also lacks the `verified` key entirely, so a consumer cannot tell it went unchecked.
Severity and impact
High. The verify-on-read tamper exclusion is a stated trust guarantee, and search is a primary read surface. A forged ESTABLISHED finding that query correctly rejects is served by search as genuine, with no marker that verification was skipped.
Location
- `mareforma/db/core.py:4206` search_claims row loop applies only the PRELIMINARY-unenrolled filter, then appends
- `mareforma/db/core.py:4114` search_claims signature and docstring, which claims query_claims-identical semantics
- `mareforma/db/core.py:4023` query_claims verify-on-read call that search_claims lacks
Fix direction
Mirror `query_claims`: add a `verify_cache: dict = {}` and, inside the search_claims row loop after the include_unverified check, drop rows that fail `_row_verified_on_read(conn, d, verify_cache)`. Since the verify filter can drop rows even when `include_unverified=True`, remove the single-batch break on `include_unverified` and keep batching until `limit` survivors or the FTS5 match-set is exhausted, with the same scan ceiling `query_claims` uses. Also set `single_trust_domain` / `trust_domain_root` on surviving ESTABLISHED rows if the "same projection" promise is to hold.
Do red/green TDD: add a regression test that fails on `main`, then make it pass.
Quality bar
SOLID, DRY, KISS. Clean, readable, well-tested code. No new errors, warnings, or test failures; the full suite stays green on all supported Python versions.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
PyPImareforma |
Corregida | 0.3.8 | — | — |
0.3.8Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://nvd.nist.gov/vuln/detail/CVE-2026-71533https://github.com/mareforma/mareforma/security/advisories/GHSA-m29v-3g7g-9c63https://github.com/mareforma/mareforma/pull/58https://github.com/mareforma/mareforma/commit/8b5291792128326a22f240123659d2754446c194https://github.com/mareforma/mareformahttps://github.com/mareforma/mareforma/releases/tag/v0.3.8Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
