You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
canary-rollout.sh rollback force-moves any destination tag, including immutable release tags, without checking it is a channel #1402
Rollback accepts an arbitrary destination suffix and sends it to the privileged tag writer without confirming that it names a registered channel. A workflow dispatcher can therefore use the release-manager App to rewrite a version tag that the documented release policy requires to remain immutable.
Location:scripts/canary-rollout.sh:2528 Severity: medium · Rule: CWE-863 · Reachability: external Subsystem: Organization administration and standards deployment
Evidence
Source/control: The workflow_dispatch ring input.
Sink/decision: Passing the unchecked destination tag to _gh_move_tag, which force-updates its reference using the configured write credential.
Missing mitigation: The privileged rollback operation does not distinguish mutable channel names from immutable release names before invoking the writer.
Reachability call stack
.github/workflows/canary-rollout.yml:124 — dispatcher supplies ring
Filed from a CodeRabbit security scan (scan 2d23b5ee-606a-403f-b407-81ddebdb0115, revision 1ea9ee1fbecc). Finding IDs: 3888f0c9-506f-4f79-96ec-646d1b9ded23. CodeRabbit notes that findings relying on its stated assumptions are capped at medium severity; dismiss if an assumption does not hold.
Activity
fix(security): match rollback ring major and tier against one registr…
fix(security): restrict canary rollback to registered mutable channels (