Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
robinmoisson/staticrypt
main @ 3594426
2
Fixes
0
CVEs
HIGH
Peak severity
Highlights
Cryptographic Weakness: 1 prior fix. Scrutinize any change in this area.
cli: most-fixed (1 issue). Treat as high-risk during review.
1 high-severity fix in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Cryptographic Weakness: The application historically used weak, direct password-to-key encryption without salt or PBKDF2 key derivation, leaving encrypted files highly vulnerable to offline brute-force attacks. Developers must ensure any encryption path uses robust, salted key derivation.
Information Disclosure: Auto-decrypt passwords were leaked via plaintext URL query parameters, exposing sensitive cryptographic secrets to server logs, browser history, and HTTP Referer headers. These must be kept client-side using URL fragments.