Skip to content

feat(autofix): Update seer explorer autofix last triggered on completion#111663

Merged
Zylphrex merged 9 commits into
masterfrom
txiao/feat/update-seer-explorer-autofix-last-triggered-on-completion
Mar 30, 2026
Merged

feat(autofix): Update seer explorer autofix last triggered on completion#111663
Zylphrex merged 9 commits into
masterfrom
txiao/feat/update-seer-explorer-autofix-last-triggered-on-completion

Merge branch 'master' into txiao/feat/update-seer-explorer-autofix-la…

07df567
Select commit
Loading
Failed to load commit list.
@sentry/warden / warden: sentry-security completed Mar 27, 2026 in 3m 54s

1 issue

sentry-security: Found 1 issue (1 medium)

Medium

Group lookup not scoped by organization - potential cross-org IDOR - `src/sentry/seer/autofix/on_completion_hook.py:86-99`

The code fetches a Group by ID from state.metadata.get('group_id') without validating that the group belongs to the provided organization. While the Seer API is trusted, this is inconsistent with the existing pattern in trigger_push_changes() (lines 503-505 of autofix_agent.py) which explicitly validates group_id == group.id. If Seer ever returns incorrect metadata (bug or manipulation), this could allow updating seer_explorer_autofix_last_triggered on a group in another organization, and potentially trigger webhooks/pipelines for the wrong group.


Duration: 3m 53s · Tokens: 1.7M in / 13.7k out · Cost: $2.31 (+extraction: $0.00)

Annotations

Check warning on line 99 in src/sentry/seer/autofix/on_completion_hook.py

See this annotation in the file changed.

@sentry-warden sentry-warden / warden: sentry-security

Group lookup not scoped by organization - potential cross-org IDOR

The code fetches a Group by ID from `state.metadata.get('group_id')` without validating that the group belongs to the provided organization. While the Seer API is trusted, this is inconsistent with the existing pattern in `trigger_push_changes()` (lines 503-505 of autofix_agent.py) which explicitly validates `group_id == group.id`. If Seer ever returns incorrect metadata (bug or manipulation), this could allow updating `seer_explorer_autofix_last_triggered` on a group in another organization, and potentially trigger webhooks/pipelines for the wrong group.