CVE-2025-64150

5.4 MEDIUM

📋 TL;DR

This vulnerability in Jenkins Publish to Bitbucket Plugin allows attackers with Overall/Read permission to connect to attacker-controlled URLs using stolen Jenkins credentials. Attackers can capture credentials stored in Jenkins, potentially compromising sensitive systems. Only Jenkins instances with this specific plugin installed are affected.

💻 Affected Systems

Products:
  • Jenkins Publish to Bitbucket Plugin
Versions: 0.4 and earlier
Operating Systems: All platforms running Jenkins
Default Config Vulnerable: ⚠️ Yes
Notes: Requires attacker to have Overall/Read permission and access to credential IDs through other means.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers exfiltrate all Jenkins credentials, gaining access to downstream systems like source code repositories, deployment servers, and cloud infrastructure.

🟠

Likely Case

Attackers capture some Jenkins credentials and use them to access connected systems, potentially leading to data theft or unauthorized deployments.

🟢

If Mitigated

With proper credential management and network segmentation, impact is limited to credential exposure without downstream access.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Requires attacker to have Jenkins user account with Overall/Read permission and knowledge of credential IDs.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 0.5 or later

Vendor Advisory: https://www.jenkins.io/security/advisory/2025-10-29/#SECURITY-3576

Restart Required: No

Instructions:

1. Access Jenkins web interface
2. Navigate to Manage Jenkins > Manage Plugins
3. Go to Available tab
4. Search for 'Publish to Bitbucket Plugin'
5. Install version 0.5 or later
6. No restart required

🔧 Temporary Workarounds

Remove plugin

all

Uninstall the vulnerable plugin if not needed

Manage Jenkins > Manage Plugins > Installed tab > Find 'Publish to Bitbucket Plugin' > Uninstall

Restrict permissions

all

Limit Overall/Read permissions to trusted users only

Manage Jenkins > Manage and Assign Roles > Configure Global Security > Set appropriate role-based permissions

🧯 If You Can't Patch

  • Implement strict credential management with minimal privileges
  • Monitor Jenkins logs for suspicious connection attempts to external URLs

🔍 How to Verify

Check if Vulnerable:

Check plugin version in Manage Jenkins > Manage Plugins > Installed tab > Find 'Publish to Bitbucket Plugin'

Check Version:

curl -s http://jenkins-host/pluginManager/installed | grep -A5 'Publish to Bitbucket Plugin'

Verify Fix Applied:

Verify plugin version is 0.5 or later in the Installed plugins list

📡 Detection & Monitoring

Log Indicators:

  • Jenkins logs showing connections to unusual external URLs
  • Failed authentication attempts using Jenkins credentials

Network Indicators:

  • Outbound connections from Jenkins server to unknown IPs on ports 80/443
  • Unusual traffic patterns from Jenkins to external services

SIEM Query:

source="jenkins.log" AND ("Publish to Bitbucket" OR "bitbucket" OR "external connection")

🔗 References

📤 Share & Export