GHSA-9H3H-67F3-W73H
WebSocket database events expose non-public fields and fail open on missing row metadata
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-9H3H-67F3-W73H divulgada | |
| Remediación | Parche v0.13.45 | github.com/daptin/daptin · 0 d desde divulgación | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
WebSocket database events delivered through `/live` were serialized from internal resource rows without applying public resource column visibility rules. Otherwise authorized row readers could receive stored password values and columns marked `ExcludeFromApi` that public API responses redact or omit. Internal numeric IDs and deletion authorization metadata could also be included.
The system-topic listener also defaulted to allow-all permissions when an event's `__type` metadata was missing or unknown, rather than rejecting the database event. This is a fail-open authorization defect for malformed internal database events; investigation did not establish a public request path that produces such an event.
Investigation and scope
The original report claimed that all ordinary update events omit `__type` and therefore bypass row authorization across users and tenants. That specific claim did not reproduce on the investigated pre-fix HEAD (`7e5d7fa2`). The pinned `github.com/artpar/api2go/v2 v2.7.4` adds `__type` in `GetAllAsAttributes()`, which ordinary resource updates return. The v0.13.44 release pins the same dependency.
An isolated two-user application test confirmed that an ordinary update carried `__type`, reached its owner, and did not reach an unrelated subscriber during a bounded observation. The owner's event did contain the stored password hash. Source inspection confirmed that event serialization bypassed the public model's password and excluded-column filtering. The broad claim that any subscriber receives every ordinary update is therefore not presented as verified impact.
Impact
Access to a resource row should not expose fields that Daptin deliberately redacts or excludes from public responses. Pre-fix database event delivery did not preserve that boundary. The missing/unknown-type fallback additionally allowed malformed database events to skip row read authorization. This finding does not demonstrate compromise of the internal Olric PubSub service or a public method for forging database event envelopes.
Resolution
Fixed in commit `b769feef3ff704f37869486b0b372c9445ee42a9` https://github.com/daptin/daptin/commit/b769feef3ff704f37869486b0b372c9445ee42a9, pushed to the default branch on 2026-10-31.
- Database events are bound to the subscribed table and require matching event metadata and a valid public reference ID. Malformed, unknown, and mismatched events are discarded.
- Create and update delivery uses current persisted row permissions and `PermissionInstance.CanRead`; event-supplied owner and permission values do not grant access.
- Delete delivery uses the existing permission snapshot captured by the resource lifecycle before deleting the row and its relationships.
- Database payloads use public model column filtering and remove internal numeric IDs and authorization metadata before reaching subscribers.
- Explicitly published custom messages retain their existing permission path and cannot select database authorization through payload attributes.
- Invalid binary string lengths are rejected before allocation.
The fix is released in v0.13.45 https://github.com/daptin/daptin/releases/tag/v0.13.45. Upgrade to v0.13.45 or later. Operators unable to upgrade can restrict access to `/live` as a temporary mitigation.
Validation
Passed against the fixed revision:
DAPTIN_REAL_E2E=1 go test ./cmd/daptin -run '^TestWebSocket(RowAuthorization|StateTransitionAuthorization)RealE2E$' -count=1
go test ./server/resource ./server/websockets -count=1
go vet ./server/resource ./server/websocketsReal application coverage exercises create/update/delete, REST and action updates, state-machine publication, owner and administrator access, group sharing and revocation, public-field filtering, both custom-message entry points, malformed binary/JSON events, missing and mismatched metadata, missing rows, and event-supplied owner/ACL values. Denial assertions use a subsequent marker on the same PubSub channel rather than treating a disconnected socket as proof of denial.
Credit
Reported by @NotAFlightRisk. Thank you for highlighting the WebSocket authorization and internal-payload boundaries.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogithub.com/daptin/daptin |
Corregida | v0.13.45 | 0 d | v0.13.57 no afectada |
0.13.45v0.13.45Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/daptin/daptin/security/advisories/GHSA-9h3h-67f3-w73hLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
