StateStore RPCs ReadTaskLog and StreamTaskLogContent (proto/state/v1/state.proto, handlers in internal/infrastructure/staterpc/server.go), backed by TaskRegistry.TaskLog and TaskLogContent in internal/logging/reader.go: they take only a task ID and attempt, with no org check, so any caller can read another org's task logs by ID. The dashboard routes check ownership first with TaskByID; the RPC does not. Done when the RPC confirms the task is in the caller's org before reading its log.
Acceptance criteria
Both task-log RPCs verify task ownership against the caller organization before returning log data.
Imported from beads archie-core-kgxw.24 · GitHub #1591 · type bug · priority P1 · created 2026-10-10 · closed 2026-10-11
StateStore RPCs ReadTaskLog and StreamTaskLogContent (proto/state/v1/state.proto, handlers in internal/infrastructure/staterpc/server.go), backed by TaskRegistry.TaskLog and TaskLogContent in internal/logging/reader.go: they take only a task ID and attempt, with no org check, so any caller can read another org's task logs by ID. The dashboard routes check ownership first with TaskByID; the RPC does not. Done when the RPC confirms the task is in the caller's org before reading its log.
### Acceptance criteria
Both task-log RPCs verify task ownership against the caller organization before returning log data.
### Close reason
Fixed on feat/org-epic (PR #1634)
---
_Imported from beads `archie-core-kgxw.24` · GitHub #1591 · type bug · priority P1 · created 2026-10-10 · closed 2026-10-11_
sam
added the highbug labels 2026-10-27 13:35:48 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
StateStore RPCs ReadTaskLog and StreamTaskLogContent (proto/state/v1/state.proto, handlers in internal/infrastructure/staterpc/server.go), backed by TaskRegistry.TaskLog and TaskLogContent in internal/logging/reader.go: they take only a task ID and attempt, with no org check, so any caller can read another org's task logs by ID. The dashboard routes check ownership first with TaskByID; the RPC does not. Done when the RPC confirms the task is in the caller's org before reading its log.
Acceptance criteria
Both task-log RPCs verify task ownership against the caller organization before returning log data.
Close reason
Fixed on feat/org-epic (PR #1634)
Imported from beads
archie-core-kgxw.24· GitHub #1591 · type bug · priority P1 · created 2026-10-10 · closed 2026-10-11