-
Notifications
You must be signed in to change notification settings - Fork 93
add security workflow for main #9085
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
.github/workflows/security.yml
Outdated
| name: Security | ||
| jobs: | ||
| security: | ||
| uses: KittyCAD/gha-workflows/.github/workflows/security.yml@security |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using a mutable branch reference (@security) for a reusable workflow is a security vulnerability. If the security branch in KittyCAD/gha-workflows is compromised or modified, malicious code will execute with access to all repository secrets (secrets: inherit on line 13).
Impact: Supply chain attack vector that could lead to:
- Unauthorized access to all repository secrets
- Arbitrary code execution in the CI environment
- Potential credential theft or repository compromise
Fix: Pin to an immutable reference:
uses: KittyCAD/gha-workflows/.github/workflows/security.yml@<commit-sha>
# or use a version tag
uses: KittyCAD/gha-workflows/.github/workflows/[email protected]| uses: KittyCAD/gha-workflows/.github/workflows/security.yml@security | |
| uses: KittyCAD/gha-workflows/.github/workflows/security.yml@v1.0.0 |
Spotted by Graphite Agent
Is this helpful? React 👍 or 👎 to let us know.
this will invoke a bunch of analysis tools. Right now it only collects the SBOM