GHSA-5XPP-9VVC-R5VF
Onboarding action-lockdown regression and transient action privileges permit anonymous schema download and protected-topic publication
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-5XPP-9VVC-R5VF divulgada · CVSS 6.5 (GitHub) | |
| 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
This report covers two interacting authorization problems:
- Administrator onboarding left bootstrap-open actions anonymously executable because the general ownership transition rewrote their permission value before the action-specific lockdown matched it.
- Once a caller was allowed to invoke `publish_to_topic`, the publisher checked target-topic permissions using the action execution session's temporarily appended administrator membership. This made the topic check ineffective for that action path.
The schema-download portion overlaps GHSA-gc3f-vmqj-j7hw https://github.com/daptin/daptin/security/advisories/GHSA-gc3f-vmqj-j7hw. This advisory additionally documents the confirmed topic-publication effect and its separate permission boundary.
Confirmed impact and scope
On an affected instance after normal administrator onboarding, an anonymous caller could download the runtime system schema/configuration catalog and publish an in-memory message to the built-in `world` topic. The reporter did not establish secret exfiltration, persistent database modification, or administrator account impersonation. Schema contents can include deployment-specific operational configuration, but the reported default dump did not contain `encryption.secret` or `jwt.secret`.
Maintainers independently confirmed the topic boundary using an isolated local instance and an administrator WebSocket subscriber. After the onboarding sequencing fix, fresh defaults denied anonymous and ordinary-user invocation of `publish_to_topic` with HTTP 403. When an administrator explicitly granted only permission to invoke that action, the old publisher still allowed both an ordinary user and an anonymous caller to publish to `world`. The subscriber received both messages. The ordinary user's direct WebSocket publication was denied before and after the action-only permission change.
That experiment distinguishes permission to invoke the wrapper action from permission to publish to its requested topic. Granting the first is not intended to bypass the second.
Root cause
The onboarding regression was introduced in 905bed49 https://github.com/daptin/daptin/commit/905bed49, first tagged as `v0.12.28`. The generic ownership pass changed bootstrap action permissions from `2097151` to `561441`, retaining `GuestExecute`. The subsequent action lockdown matched only the original `2097151`, so it skipped those actions. Explicit signup lockdown later protected signup without repairing the other affected actions.
Separately, `HandleActionRequest` appends the administrator group while executing trusted action outcomes. `action_publish_to_topic.go` previously passed those augmented groups to `PermissionInstance.CanCreate` for system topics and `CanExecute` for custom topics. The transient administrator membership satisfied the checks even when the active account's persisted memberships did not authorize publication.
Fixes
Both fixes are pushed to `master`:
- dec3fee4
https://github.com/daptin/daptin/commit/dec3fee4runs the existing action lockdown before the generic ownership transition, preserving explicit public/private action policies while correctly restricting bootstrap-open actions during onboarding. - 3a6010b3
https://github.com/daptin/daptin/commit/3a6010b3makes the publisher resolve the active account's persisted memberships through the existing resource helper and transaction. Topic checks no longer use transient action privileges. Anonymous callers have no persisted memberships. Actual administrators, custom-topic owners, explicit grants, and intentional guest permissions retain their existing semantics. After `SWITCH_USER`, publication follows the selected account.
The publisher fix is local to topic authorization; it does not remove trusted execution privileges from the general action engine or assert that every other performer has been audited.
Both fixes are released in v0.13.45 https://github.com/daptin/daptin/releases/tag/v0.13.45. Upgrade to v0.13.45 or later and review persisted grants as described below. The reporter identified source commit `4b2e5ffdb31cb2dd20a9c6569263888246603181` as v0.13.2; maintainers also reproduced the topic issue on later source before the publisher fix. The affected publisher implementation is also present in v0.13.44. Versions before 0.13.45 are treated as affected by the topic-permission issue; every earlier tag has not been independently reproduced. The combined default-onboarding effect begins at v0.12.28. The original `<= 0.13.2` range does not imply that newer releases are unaffected.
Existing installations and remediation
Upgrading does not rerun first-administrator onboarding or indiscriminately rewrite persisted action policies. Administrators should revoke unintended `GuestExecute` grants on administrative actions, including `world/download_system_schema`, through Daptin's permissioned JSON:API `action` resource. Review intentional public application actions individually rather than blanket-rewriting all rows carrying `561441`.
The publisher fix enforces target-topic permissions even where invocation of the wrapper action remains allowed. System topics require table `CanCreate`; custom topics require the existing topic `CanExecute` grant. Explicitly configured guest topic permissions remain valid.
Until a patched build is deployed, restrict invocation of `publish_to_topic` to trusted administrators and remove unintended anonymous execution grants on affected system actions. Verify both action invocation and actual target-topic publication permissions.
Verification
`TestTopicPublishUsesPersistedPermissionsRealE2E` runs real local Daptin processes after administrator onboarding and restart, with permissions and relationships configured through resource APIs. It verifies:
- Fresh defaults deny anonymous and ordinary-user action invocation.
- After wrapper execution is explicitly granted, users and guests without topic permission are denied and no message is delivered.
- Explicit group grants permit publication; revocation denies it.
- Persisted administrators and custom-topic owners can publish.
- Explicit guest execution on a custom topic works and can be revoked.
- `SWITCH_USER` uses the selected account's persisted permissions and event source.
- Action and direct WebSocket publishing agree for authorized and unauthorized users.
The existing downstream performer error convention is preserved: a topic denial after wrapper admission returns `permission denied`, currently mapped to HTTP 500 by the action HTTP handler; wrapper-gate denial returns HTTP 403. Neither denial publishes a message.
Action, resource, and permission test suites, action `go vet`, and diff checks passed. The onboarding fix has separate composition and real HTTP regression coverage for schema download, explicit policies, ownership, signup, and signin.
Performance validation
An opt-in local PostgreSQL 17.5 benchmark compared otherwise identical binaries before and after only the publisher membership change. It used explicitly authorized ordinary users with 2 and 21 groups, 1/8/32/64 concurrent callers, three counterbalanced trials per case, three-second measurement windows, and the default 50-connection database pool. The disposable test's action-route rate limit was raised so the default 500 requests/second limit did not clip the measurement.
Across 223,708 measured publications there were zero HTTP failures, missing deliveries, or duplicate deliveries. The fixed publisher performed exactly one additional membership query per publication. Median throughput decreased approximately 4–10% across the measured cases. Both builds encountered connection-pool waits at 64 callers. Large transient slowdowns affected portions of both builds and remain included in the raw results; short local measurements do not establish production or distributed capacity.
See the benchmark source https://github.com/daptin/daptin/blob/3a6010b3/cmd/daptin/topic_publish_benchmark_test.go and all raw samples and methodology metadata https://github.com/daptin/daptin/blob/3a6010b3/scripts/testing/benchmarks/topic-publish-permissions-2026-11-02.json.
Coordination and credit
Report FO-DAPTIN-2026-001 by Wenhao Wu, Southeast University (`d3do-23`). The report states a coordinated-disclosure deadline of January 11, 2027. Medium severity is retained. The accepted report is published with the v0.13.45 security release.
Desglose de métricas
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-5xpp-9vvc-r5vfLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
