Media

Mareforma: search_claims skips verify-on-read, serving forged rows

  • Publicada: 19.11.2026
  • Actualizado: 19.11.2026 18:17

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 absent

The 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.

Software afectado

Haz clic en una tecnología para ver todas sus vulnerabilidades.

PlataformaPaqueteVersiones vulnerablesCorregida en
Python (PyPI) mareforma >= 0.3.7, < 0.3.8 0.3.8

Referencias

Puntuación CVSS -
Vector CVSS
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Debilidad (CWE)
CWE-347
Plataforma
Python (PyPI)
Paquete
mareforma
Publicada
19.11.2026
Actualizado
19.11.2026 18:17

Fuentes y licencias

OSV / GitHub Advisory Database - GHSA-m29v-3g7g-9c63 - CC BY 4.0

Historial de vulnerabilidades: mareforma

Todas las vulnerabilidades publicadas de este paquete (Python (PyPI)), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.

Entradas en total
5
Primera → última
11.2026 11.2026
Sin corrección
0
Explotada en ataques
0

Distribución por gravedad

  • Alta 2
  • Media 3

Divulgaciones por año

  1. 2026: 5
  1. Media CVE-2026-71534 >= 0.3.0, < 0.3.8 0.3.8
  2. Media CVE-2026-71500 >= 0.3.0, < 0.3.8 0.3.8
  3. Alta CVE-2026-71536 >= 0.3.0, < 0.3.8 0.3.8
  4. Mareforma: search_claims skips verify-on-read, serving forged rows esta entrada
    Media CVE-2026-71533 >= 0.3.7, < 0.3.8 0.3.8

Identifica las vulnerabilidades de tu aplicación

Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.

Conectar tu aplicación
Newsletter DockRay

La seguridad de tus aplicaciones en tu correo

Vulnerabilidades importantes, recomendaciones concretas y consejos prácticos para tus aplicaciones. Elige tus tecnologías y sigue lo que importa para tu proyecto.

  • Un resumen diario de nuevas vulnerabilidades, también las críticas.
  • Avisos sobre actualizaciones importantes.
  • Consejos prácticos sobre seguridad y monitorización de aplicaciones.

Déjalo vacío para recibir avisos de todas las tecnologías.

Suscripción gratuita. Date de baja con un clic en cualquier correo.