dbcve.org
Bitbucket Branch SourceApplication · Jenkins

CVE-2022-20619

HIGH · 7.1 CVSS v3.1 Published 2022-01-12
Fix available
A fix is available. Upgrade to after 2.9.10 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
A cross-site request forgery (CSRF) vulnerability in Jenkins Bitbucket Branch Source Plugin 737.vdf9dc06105be and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.

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

A CSRF vulnerability in Jenkins Bitbucket Branch Source Plugin 737.vdf9dc06105be and earlier allows authenticated users to be tricked into making unintended requests that connect to attacker-controlled URLs using credentials IDs the attacker has obtained separately, enabling exfiltration of stored Jenkins credentials.

MitigationUpgrade the Bitbucket Branch Source Plugin to a version newer than 737.vdf9dc06105be. If immediate upgrade is not feasible, disable the plugin until patched and review Jenkins credentials for unauthorized access.

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 Branch SourceApplication
Affected:<= 2.9.10= 737.vdf9dc06105be

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/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. Confirm Bitbucket Branch Source Plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Bitbucket Branch Source'. Alternatively, check the file system for the plugin at $JENKINS_HOME/plugins/ directory for a folder named 'bitbucket-branch-source'.
    Affected if The plugin appears in the installed list or the plugin folder exists in the plugins directory.
  2. Determine the installed plugin version
    In the Manage Plugins > Installed tab, locate Bitbucket Branch Source and read the Version column. If using CLI, check $JENKINS_HOME/plugins/bitbucket-branch-source/META-INF/MANIFEST.MF for the 'Plugin-Version' attribute.
    Affected if The version number is 2.9.10 or lower, or exactly 737.vdf9dc06105be.
  3. Verify if the plugin is active and not disabled
    In Manage Plugins > Installed tab, ensure Bitbucket Branch Source is not listed as 'Disabled'. An enabled plugin can be exploited even if not actively used in jobs.
    Affected if The plugin is installed and not explicitly disabled.
  4. Check for credentials configured with Bitbucket Branch Source
    Go to Manage Jenkins > Manage Credentials. Review any credentials with kind 'Username with password', 'SSH Username with private key', or 'Secret text' that are used for Bitbucket Cloud or Bitbucket Server integrations. Also check individual job or folder configurations under 'Branch Sources' for active Bitbucket credential usage.
    Affected if Credentials IDs for Bitbucket integration exist in Jenkins credentials store or are referenced in job configurations.

If the Bitbucket Branch Source Plugin is installed at version 2.9.10 or lower (or version 737.vdf9dc06105be), is enabled, and has credentials configured for Bitbucket connections, the environment is vulnerable to credential exfiltration via CSRF.

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.9.10
Interim mitigation

Upgrade the Bitbucket Branch Source Plugin to a version newer than 737.vdf9dc06105be. If immediate upgrade is not feasible, disable the plugin until patched and review Jenkins credentials for unauthorized access.

Recommended fix Moderate confidence

Bitbucket Branch Source Plugin version 2.9.11 or later

  1. 1. In the Jenkins dashboard, navigate to 'Manage Jenkins' → 'Manage Plugins'
  2. 2. Go to the 'Installed' tab and locate 'Bitbucket Branch Source Plugin'
  3. 3. If the plugin shows version 2.9.10 or earlier, an update is available
  4. 4. Select the plugin and click 'Update' to upgrade to the fixed version
  5. 5. After the update completes, restart Jenkins to apply the changes
  6. 6. Verify the new version is installed by checking the plugin manager again

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

Fix this in Bitbucket Branch Source Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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