OAuth token disclosure via logged Bitbucket URL
Published Jun 26, 2024 · Updated Feb 13, 2025
Sensitive-data exposure in Jenkins Bitbucket Branch Source Plugin 886.v44cf5e4ecec5 and earlier allows attackers to read OAuth tokens in build logs. The plugin embeds the Bitbucket OAuth access token in the Bitbucket URL rendered to build output instead of omitting the credential from the logged URL. Exposure occurs only in some OAuth-backed builds, and anyone permitted to view the affected build log can recover the token for Bitbucket access.
Summary
What happened
Sensitive-data exposure in Jenkins Bitbucket Branch Source Plugin 886.v44cf5e4ecec5 and earlier allows attackers to read OAuth tokens in build logs. The plugin embeds the Bitbucket OAuth access token in the Bitbucket URL rendered to build output instead of omitting the credential from the logged URL. Exposure occurs only in some OAuth-backed builds, and anyone permitted to view the affected build log can recover the token for Bitbucket access.
The record
- CVE
- CVE-2024-39460
- Published
- Jun 26, 2024
- Updated
- Feb 13, 2025
- Vendor
- Jenkins Project
- Product
- Jenkins Bitbucket Branch Source Plugin
- Classifications
- CWE-532, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 26, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=886.v44cf5e4ecec5
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