dbcve.org
Bitbucket Push And Pull RequestApplication · Jenkins

CVE-2023-41937

HIGH · 7.5 CVSS v3.1 Published 2023-09-06
Fix available
A fix is available. Upgrade to after 2.8.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Jenkins Bitbucket Push and Pull Request Plugin 2.4.0 through 2.8.3 (both inclusive) trusts values provided in the webhook payload, including certain URLs, and uses configured Bitbucket credentials to connect to those URLs, allowing attackers to capture Bitbucket credentials stored in Jenkins by sending a crafted webhook payload.

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

The Bitbucket Push and Pull Request Plugin versions 2.4.0-2.8.3 does not validate URLs received in webhook payloads. Attackers can send crafted webhooks containing malicious URLs that the plugin will access using Bitbucket credentials stored in Jenkins, enabling credential exfiltration via SSRF-style attack.

MitigationUpgrade the Bitbucket Push and Pull Request Plugin to version 2.8.4 or later, which implements proper URL validation and prevents credential usage on untrusted webhook URLs.

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 Push And Pull RequestApplication
Affected:>= 2.4.0, <= 2.8.3

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Check if Bitbucket Push and Pull Request Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Bitbucket Push and Pull Request', or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i bitbucket
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    In Jenkins > Manage Jenkins > Manage Plugins > Installed tab, locate the Bitbucket Push and Pull Request plugin and note the Version column. Alternatively, check the plugin's manifest file (META-INF/MANIFEST.MF) within the plugin's .hpi file in the Jenkins plugins directory
    Affected if The version number falls within the range >= 2.4.0 and <= 2.8.3
  3. Verify webhook configuration exists
    Navigate to Jenkins > Manage Jenkins > System Configuration > System > scroll to 'Bitbucket Push and Pull Request plugin' section, or check job configurations for any jobs using Bitbucket webhook triggers
    Affected if Webhook endpoints are configured or jobs use Bitbucket webhook triggers
  4. Confirm Bitbucket credentials are stored in Jenkins
    Navigate to Jenkins > Manage Jenkins > Manage Credentials and check for any credentials associated with Bitbucket (look for 'Bitbucket' in the Kind column or source URLs containing bitbucket.org)
    Affected if Bitbucket credentials (username/password, API token, or SSH key) are stored in Jenkins credentials store

A user is affected if the Bitbucket Push and Pull Request Plugin version is between 2.4.0 and 2.8.3 inclusive AND webhook endpoints are configured with Bitbucket credentials present in Jenkins.

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 a release after 2.8.3
Interim mitigation

Upgrade the Bitbucket Push and Pull Request Plugin to version 2.8.4 or later, which implements proper URL validation and prevents credential usage on untrusted webhook URLs.

Recommended fix High confidence

Upgrade to Bitbucket Push and Pull Request plugin version 2.8.4 or latest available

  1. Navigate to Jenkins dashboard > Manage Jenkins > Manage Plugins
  2. Go to the 'Installed' tab and locate 'Bitbucket Push and Pull Request' plugin
  3. Click 'Update now' to fetch the latest available version
  4. Restart Jenkins if required to complete the installation
  5. Verify the plugin version is updated to 2.8.4 or later

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

Fix this in Bitbucket Push And Pull Request Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41937 — 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-2023-41937 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