Pipeline manipulation via overbroad fork trust
Published Mar 6, 2024 · Updated Feb 13, 2025
Improper authorization in Jenkins Bitbucket Branch Source Plugin 866.vdea_7dcd3008e and earlier allows remote attackers to alter Pipeline behavior. The Forks in the same account policy trusts a forked pull request's modified Jenkinsfile without verifying that its author has project write access. Exploitation requires Bitbucket Server, fork pull-request discovery, and that trust policy; Bitbucket Cloud pipelines are unaffected.
Summary
What happened
Improper authorization in Jenkins Bitbucket Branch Source Plugin 866.vdea_7dcd3008e and earlier allows remote attackers to alter Pipeline behavior. The Forks in the same account policy trusts a forked pull request's modified Jenkinsfile without verifying that its author has project write access. Exploitation requires Bitbucket Server, fork pull-request discovery, and that trust policy; Bitbucket Cloud pipelines are unaffected.
The record
- CVE
- CVE-2024-28152
- Published
- Mar 6, 2024
- Updated
- Feb 13, 2025
- Vendor
- Jenkins Project
- Product
- Jenkins Bitbucket Branch Source Plugin
- Classifications
- CWE-281, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 6, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo