p PatchFirst

GHSA-9gjv-jvm7-vv2v

GHSA-9gjv-jvm7-vv2v · Gramps Web API: Private Sub-Object Data in Non-Private Objects Exposed to Guest Users

Esta página presenta datos de fuentes públicas de vulnerabilidades. Consulta el aviso original antes de actualizar.

## Summary Users with the **Guest** role could receive private sub-object data (e.g. private alternate names, private addresses, private note/citation/media handles) through list API endpoints such as `GET /api/people/`, `GET /api/places/`, `GET /api/events/`, and all other object list endpoints. **This does not expose objects (people, places, events, …) that are themselves marked private.** Top-level private objects are correctly excluded from all responses. Only sub-object data attached to otherwise-public objects is affected. ## Affected Versions All versions of Gramps Web API prior to the fix. ## Root Cause The vulnerability originates from the behaviour of `PrivateProxyDb.iter_*()` in **Gramps core**. The `ProxyDbBase.__iter_object()` helper, which backs all `iter_*()` methods in `PrivateProxyDb`, correctly filters out top-level private objects but returns the remaining objects **unsanitized** — i.e. without stripping private sub-object references. In contrast, `PrivateProxyDb.get_*_from_handle()` does call the appropriate `sanitize_*()` function. Gramps Web API's `ModifiedPrivateProxyDb` (which wraps the raw database for non-admin users) inherited this behaviour without override. The same issue affects Gramps desktop features that consume `iter_*()` output: reports and exports generated via Gramps desktop using `PrivateProxyDb` may also include private sub-object data that should have been stripped. ## Conditions Required **This issue only affects trees in which sub-objects have been explicitly marked private in Gramps desktop.** The Gramps Web frontend UI does not expose controls for setting the private flag on sub-objects (alternate names, addresses, notes, citations, media references, event references, etc.). In practice, such flags are set in Gramps desktop and then synced or imported into Gramps Web. ## Impact When the conditions above are met, a user with the Guest role querying any list endpoint receives: - **Full content** of private embedded sub-objects on people, such as alternate names (first name, surname, etc.) and addresses (street, city, etc.). - **Handles referencing** private notes, citations, and media attached to places, events, sources, and other objects. These reveal the *existence* of private linked objects but not their content; fetching those objects by handle is correctly blocked by the proxy. ## Fix `ModifiedPrivateProxyDb` now overrides all `iter_*()` object methods to check `obj.get_privacy()` directly on the already-loaded object (eliminating the redundant per-object refetch) and to call the appropriate `sanitize_*()` function before yielding each object. This is consistent with the behaviour of `get_*_from_handle()` in `PrivateProxyDb`.

CVSS 6.9 · Media · Corrección disponible

Publicación
Actualización

Pila tecnológica: python

Productos y versiones afectados

  • gramps-webapi PyPI

    Versiones
    • 0.1
    • 0.2.1
    • 0.2.2
    • 0.2.3
    • 0.3.0
    • 0.3.1
    • 0.3.2
    • 0.4.0
    • 0.4.1
    • 0.4.2
    • 0.4.3
    • 0.4.4
    • 0.5.0
    • 0.5.1
    • 0.6.0
    • 0.6.1
    • 0.7.0
    • 1.0.0
    • 1.1.0
    • 1.1.1
    • 1.1.10
    • 1.1.11
    • 1.1.2
    • 1.1.3
    • 1.1.4
    • 1.1.5
    • 1.1.6
    • 1.1.7
    • 1.1.8
    • 1.1.9
    • 1.2.0
    • 1.2.1
    • 1.3.0
    • 1.3.1
    • 1.3.2
    • 1.4.0
    • 1.4.1
    • 1.4.2
    • 1.5.0
    • 1.5.1
    • 1.6.0
    • 2.0.0
    • 2.1.0
    • 2.2.0
    • 2.2.1
    • 2.3.0
    • 2.3.1
    • 2.4.0
    • 2.4.1
    • 2.4.2
    • 2.4.3
    • 2.5.0
    • 2.5.1
    • 2.5.2
    • 2.5.3
    • 2.6.0
    • 2.7.0
    • 2.8.0
    • 2.8.1
    • 2.8.2
    • 2.9.0
    • 2.9.1
    • 2.9.2
    • 3.0.0
    • 3.0.1
    • 3.0.2
    • 3.1.0
    • 3.10.0
    • 3.2.0
    • 3.3.0
    • 3.4.0
    • 3.4.1
    • 3.5.0
    • 3.6.0
    • 3.7.0
    • 3.7.1
    • 3.8.0
    • 3.9.0
    • 3.9.1
    Intervalos de versiones afectados
    • ECOSYSTEM: < 3.11.0

    Actualiza a 3.11.0

Fuentes originales

Comprueba tu servidor →