Skip to content

fix(security): probe argument-injection + same-owner alert routing - #47

Merged
ClaraVnk merged 1 commit into
mainfrom
feat/sec-probe-routing
Jun 30, 2026
Merged

fix(security): probe argument-injection + same-owner alert routing#47
ClaraVnk merged 1 commit into
mainfrom
feat/sec-probe-routing

Conversation

@ClaraVnk

Copy link
Copy Markdown
Contributor

Pentest remediation (probes + alert routing). Findings #5, #9.

Plus a test-hygiene fix isolating the zk CLI tests' env (removes a pre-existing
order-dependent flake). Full suite 228 passed; ruff + mypy(strict) green.

Two more pentest items, both defense-in-depth:

- ping argument injection: the user-controlled target is now passed after a `--`
  separator, so a monitor target like `-w99999` can't be read as a ping flag (still
  argv, never a shell — no command injection either way).
- same-owner alert routing: the dispatcher's monitor/host channel lookups and the
  escalation engine now additionally require the channel's owner to match the
  entity's/problem's owner. Today the write paths already prevent cross-owner links,
  so this is belt-and-suspenders against a future path that forgets the check.

Tests: ping inserts `--` before the target; escalation refuses to deliver a problem
through another owner's channel. Also isolate the zk CLI tests' env to remove a
pre-existing order-dependent flake. Full suite 228 passed; ruff + mypy(strict) green.
@ClaraVnk
ClaraVnk merged commit ae94281 into main Jun 30, 2026
4 checks passed
@ClaraVnk
ClaraVnk deleted the feat/sec-probe-routing branch June 30, 2026 21:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant