Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

semaphoreui/semaphore

              develop @ c59c3dc
            

Fixes

CVEs

CRITICAL

Peak severity

55.0%

Coverage

Highlights

Auth Bypass: 18 prior fixes. Scrutinize any change in this area.

api: most-fixed (4 issues). Treat as high-risk during review.

24 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: The authentication handler was historically vulnerable to critical logic failures, such as Proceeding to call next.ServeHTTP despite explicit authentication failures and incorrectly evaluating recovery code hashes.

Auth Bypass: A critical flaw in permission evaluation used a self-bitwise AND operation (userPermissions & userPermissions) == permissions instead of evaluating against target permissions, causing wide-reaching authorization bypasses in project operations.

Argument Injection: Lack of validation on repository URLs allowed untrusted branches and URLs to inject CLI arguments into downstream git commands, requiring mitigation with '--end-of-options' boundaries and strict pattern validation.