[Security] HIGH: 9 issue(s) found in animsuite #24
Labels
No labels
blocked:commit-ready-failed
blocked:needs-decision
blocked:needs-human
blocked:no-procedure
blocked:preflight
blocked:verify-failed
bug
feature-request
in-progress
lint-cleanup
ops-task
quickfix
triage-approved
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/animsuite#24
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Security Scan Results for
animsuiteSeverity: HIGH
Findings: 9
1. secret_in_diff
491ea179AWS Secret Key2. secret_in_diff
ff0da7b2AWS Secret Key3. secret_in_diff
3011ff66AWS Secret Key4. secret_in_diff
623d32d9AWS Secret Key5. secret_in_diff
6f074eecAWS Secret Key6. secret_in_diff
1448e0ff1448e0ffAWS Secret Key7. secret_in_diff
1cdb4cf81cdb4cf8AWS Secret Key8. secret_in_diff
b1f52274b1f52274AWS Secret Key9. vulnerable_dependency
This issue was auto-generated by the security sweep cron job.
Feature Triage Assessment
Scope: small
Risk: low
Spec Alignment: misaligned
Summary: All 9 findings are security scanner false positives: 8 SHA hashes in .gsd/gate-state.json are misidentified as AWS Secret Keys, and pillow (v12.1.0 installed) is flagged for CVE-2023-4863 which affects <10.0.1 — the unpinned requirements.txt entry alone triggers the scanner.
Recommendation: Close as false positive with rationale. Optionally: (a) pin pillow version in requirements.txt/pyproject.toml to suppress the CVE alert, and (b) add .gsd/*.json to the scanner's exclude list so commit SHAs stop triggering AWS key pattern matches. No code changes needed.
Rationale: Scope: trivial — no code changes needed, just config changes if any. Risk: low — no actual credentials leaked (the 'secrets' are git commit SHAs in GSD gate-state JSON files); pillow is at 12.1.0, far above the CVE-2023-4863 threshold. Spec: misaligned — there is no real vulnerability to address.
Labeled
blocked:needs-decision— unblock on Forgejo to dispatch to the fixer pipeline.No longer reproducible — gitleaks scan shows 0 findings in current tree and git history. These were likely in old commits that have since been cleaned up or were false positives resolved by code changes.
Closing as resolved.