# CVE-2024-28152: Jenkins Bitbucket Branch Source Plugin has incorrect trust policy behavior for pull requests

> Attackers without write access can modify Jenkinsfiles via fork trust policy, leading to code execution in Jenkins.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Mar 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-m4rm-x2rr-357w

## What is CVE-2024-28152?

CVE-2024-28152 is a medium-severity missing authorization vulnerability in Jenkins Bitbucket Branch Source Plugin, published on 6 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-281 (Improper Preservation of Permissions)

## Which versions are affected by CVE-2024-28152?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source` | Maven | All versions | 871.v28d74e8b_4226 |
| `org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source` | Maven | All versions | 871.v28d74e8b_4226 |

Products: Jenkins Bitbucket Branch Source.

## How do I fix CVE-2024-28152?

Upgrade org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 871.v28d74e8b_4226 or later.

## Is CVE-2024-28152 being exploited?

There is no known exploitation of CVE-2024-28152 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins Bitbucket Branch Source Plugin

- [CVE-2022-20619](https://insights.sbomify.com/CVE-2022-20619/): Cross-Site Request Forgery in Jenkins Bitbucket Branch Source Plugin (high 7.1)
- [CVE-2024-39460](https://insights.sbomify.com/CVE-2024-39460/): Bitbucket OAuth access token exposed in the build log by Bitbucket Branch Source Plugin (medium 4.3)
- [CVE-2022-20618](https://insights.sbomify.com/CVE-2022-20618/): Incorrect Permission Assignment for Critical Resource in Jenkins Bitbucket Branch Source Plugin (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28152 and fix it if it is affected.

What it is: CVE-2024-28152 is a medium-severity missing authorization vulnerability in Jenkins Bitbucket Branch Source Plugin, published on 6 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-28152 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven): affected all versions; fixed in 871.v28d74e8b_4226
- org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven): affected all versions; fixed in 871.v28d74e8b_4226

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-28152/ (Markdown: https://insights.sbomify.com/CVE-2024-28152/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-28152
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-28152
- OSV: https://osv.dev/vulnerability/CVE-2024-28152

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-28152/
Summaries are generated and may contain mistakes; the official description above is the record.