Remove vulnerable cli-proxy 0.27.44 container pin - #52934
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
|
Great work addressing the container vulnerability! 🛡️ This PR cleanly removes the vulnerable What's working well:
This looks ready for review. The diff is small (13 additions, 15 deletions), well-scoped, and addresses the security concern from issue #52651 directly.
|
There was a problem hiding this comment.
Pull request overview
Removes the vulnerable cli-proxy:0.27.44 digest from canonical and embedded container-pin metadata.
Changes:
- Removes the vulnerable pin from all three catalogs.
- Adds regression coverage preventing reintroduction.
- Adds patch release metadata.
Show a summary per file
| File | Description |
|---|---|
.github/aw/actions-lock.json |
Removes the canonical vulnerable pin. |
pkg/actionpins/data/action_pins.json |
Updates the embedded pin catalog. |
pkg/workflow/data/action_pins.json |
Synchronizes workflow pin data. |
pkg/actionpins/actionpins_internal_test.go |
Verifies the image cannot be resolved from embedded metadata. |
.changeset/patch-remove-vulnerable-awf-0-27-44-cli-proxy-pin.md |
Documents the security-related patch. |
Review details
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
- Files reviewed: 5/5 changed files
- Comments generated: 0
- Review effort level: Balanced
|
🎉 This pull request is included in a new release. Release: |
The pinned
cli-proxy:0.27.44image contains multiple high-severity Node.js and npm dependency vulnerabilities. The default firewall version already uses the unaffected0.28.1image.Container pins
cli-proxy:0.27.44from canonical lock data.Regression coverage
Release metadata