Security context

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

jenkinsci/gitlab-plugin

              master @ b84335d
            

Fixes

CVEs

HIGH

Peak severity

42.9%

Coverage

Highlights

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

src/main/java/com/dabsquared/gitlabjenkins/GitLabPushTrigger.java: most-fixed (2 issues). Treat as high-risk during review.

2 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 plugin previously cached GitLab clients globally under the first initialized client rather than keying them per API token, enabling subsequent users to perform actions using the cached, privileged connection.

Auth Bypass: The connection testing endpoint was exposed to users possessing only global read permissions (Jenkins.READ) instead of enforcing proper configuration permissions (Item.CONFIGURE).

Credential Exposure: GitLab API token retrieval was globally scoped instead of restricted to the targeted GitLab URL domain, leaking credentials outside their intended environment.