dbcve.org
Bitbucket Branch SourceApplication · Jenkins

CVE-2024-28152

MEDIUM · 6.3 CVSS v3.1 Published 2024-03-06
Fix available
A fix is available. Upgrade to 848.850.v6a_a_2a_234a_c81 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
In Jenkins Bitbucket Branch Source Plugin 866.vdea_7dcd3008e and earlier, except 848.850.v6a_a_2a_234a_c81, when discovering pull requests from forks, the trust policy "Forks in the same account" allows changes to Jenkinsfiles from users without write access to the project when using Bitbucket Server.

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 confidence

In Jenkins Bitbucket Branch Source Plugin, the trust policy 'Forks in the same account' incorrectly allows users without write access to modify Jenkinsfiles in pull requests from forks when using Bitbucket Server. This enables potential privilege escalation where untrusted fork contributors could alter build pipeline configurations.

MitigationUpdate Bitbucket Branch Source Plugin to version 848.850.v6a_a_2a_234a_c81 or later, or review and restrict fork trust policies to prevent untrusted users from modifying Jenkinsfiles.

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
Bitbucket Branch SourceApplication
Affected:< 848.850.v6a_a_2a_234a_c81= 856.v04c46c86f911= 866.vdea_7dcd3008e

CVSS 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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Bitbucket Branch Source Plugin
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Bitbucket Branch Source' to confirm it is installed.
    Affected if Plugin is not installed - not vulnerable
  2. Check the installed plugin version
    In the Installed plugins list, note the version number of Bitbucket Branch Source Plugin. Versions below 848.850.v6a_a_2a_234a_c81, or exactly 856.v04c46c86f911, or exactly 866.vdea_7dcd3008e are affected.
    Affected if Installed version matches one of the affected ranges listed
  3. Identify Bitbucket Server usage
    Review configured multibranch pipeline jobs or Bitbucket Branch Source configuration to determine if Bitbucket Server (not Bitbucket Cloud) is the configured SCM.
    Affected if Bitbucket Server is configured - vulnerability applies only to Bitbucket Server setups
  4. Inspect fork trust policy settings
    In Jenkins job configuration under Branch Sources > Bitbucket Server, locate the 'Trust' policy setting for forks. Check if it is set to 'Forks in the same account'.
    Affected if Trust policy is set to 'Forks in the same account' and the conditions above are met

User is affected if Bitbucket Branch Source Plugin is installed with an affected version, Bitbucket Server is configured, and the fork trust policy is set to 'Forks in the same account'.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 848.850.v6a_a_2a_234a_c81 or later
Fixed in 848.850.v6a_a_2a_234a_c81
Interim mitigation

Update Bitbucket Branch Source Plugin to version 848.850.v6a_a_2a_234a_c81 or later, or review and restrict fork trust policies to prevent untrusted users from modifying Jenkinsfiles.

Recommended fix Moderate confidence

Upgrade to Bitbucket Branch Source Plugin version 848.850.v6a_a_2a_234a_c81 or later

  1. 1. Navigate to Jenkins Dashboard > Manage Jenkins > Manage Plugins
  2. 2. Go to the "Installed" tab and locate "Bitbucket Branch Source Plugin"
  3. 3. Check the current version of the plugin
  4. 4. If the installed version is 856.v04c46c86f911 or 866.vdea_7dcd3008e, or any version before 848.850.v6a_a_2a_234a_c81, an upgrade is required
  5. 5. Click "Check now" for updates or go to the "Updates" tab
  6. 6. Select the Bitbucket Branch Source Plugin and click "Download now and install after restart"
  7. 7. Wait for the plugin to download and install
  8. 8. Restart Jenkins to apply the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bitbucket Branch Source Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28152 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-28152 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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