Github Branch SourceApplication · Jenkins
CVE-2024-23901
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins GitLab Branch Source Plugin 684.vea_fa_7c1e2fe3 and earlier unconditionally discovers projects that are shared with the configured owner group, allowing attackers to configure and share a project, resulting in a crafted Pipeline being built by Jenkins during the next scan of the group.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins GitLab Branch Source Plugin unconditionally discovers all GitLab projects shared with the configured owner group without proper authorization checks. Attackers can create and share a malicious pipeline project with the owner group, which Jenkins will automatically discover and execute during the next group scan.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Github Branch SourceApplication
<= 684.vea_fa_7c1e2fe3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify GitLab Branch Source Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'GitLab Branch Source' or 'GitLab' in the plugin listAffected if The plugin appears in the installed list and its version is <= 684.vea_fa_7c1e2fe3
-
Confirm the installed plugin versionIn the Installed plugins list, locate the GitLab Branch Source Plugin and note the version number shown in the 'Version' columnAffected if Version displays as 684.vea_fa_7c1e2fe3 or lower
-
Identify configured owner groupsNavigate to Jenkins > Manage Jenkins > Configure System > GitLab > and check for any 'Owner' or 'Group' configuration fields under the GitLab Branch Source settings or in the folder configuration where the plugin is usedAffected if One or more owner groups are configured, meaning Jenkins will scan and discover projects shared with those groups
-
Review project sharing permissions in GitLabIn GitLab, examine which projects members can share with the owner groups configured in Jenkins, or check if any unknown projects have recently become visible to Jenkins that were not previously discoveredAffected if Users have permission to share projects with the configured owner groups, allowing them to inject malicious pipeline configurations into Jenkins scans
You are affected if the GitLab Branch Source Plugin version is 684.vea_fa_7c1e2fe3 or lower AND owner groups are configured in Jenkins, as unauthorized projects shared with those groups will be automatically discovered and executed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the GitLab Branch Source Plugin to the latest version. If immediate updating is not possible, review and restrict which GitLab groups are configured as owner groups in Jenkins, and limit project sharing permissions.
Fix this in Github Branch Source
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23901 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23901 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data