Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
router-for-me/CLIProxyAPI
main @ f0de1d0
13
Fixes
0
CVEs
HIGH
Peak severity
50.0%
Coverage
Highlights
Auth Bypass: 5 prior fixes. Scrutinize any change in this area.
internal/api/handlers/management/auth_files.go: most-fixed (2 issues). Treat as high-risk during review.
7 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Auth Bypass: Management routes were exposed without authentication and later relied on spoofable ClientIP; both fixed, but the pattern suggests other route groups may lack consistent auth middleware.
Auth Bypass: Plugin virtual auth records could be modified/deleted directly, bypassing source-of-truth controls; also path traversal in auth file names. These fixes protect the auth file store, but sibling APIs may still lack the same validation.
Auth Bypass: Watcher events could delete tracked auth files unless explicitly initiated; the guard is message-prefix based and may be bypassed by other commit paths.