dbcve.org
Bitbucket Server IntegrationApplication · Jenkins

CVE-2022-28133

MEDIUM · 5.4 CVSS v3.1 Published 2022-03-29
Fix available
A fix is available. Upgrade to after 3.1.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Server Integration Plugin 3.1.0 and earlier does not limit URL schemes for callback URLs on OAuth consumers, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to create BitBucket Server consumers.

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 Jenkins Bitbucket Server Integration Plugin versions 3.1.0 and earlier fails to restrict URL schemes for OAuth consumer callback URLs, allowing stored XSS injection when attackers create malicious Bitbucket Server consumers with crafted callback URLs containing JavaScript payloads.

MitigationUpgrade the Jenkins Bitbucket Server Integration Plugin to version 3.1.1 or later, which implements proper URL scheme validation. Additionally, audit existing OAuth consumer configurations and restrict permissions for consumer creation to trusted users.

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 Server IntegrationApplication
Affected:<= 3.1.0

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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. Verify Bitbucket Server Integration plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Bitbucket Server Integration' in the list of installed plugins.
    Affected if The plugin is not found in the installed plugins list, meaning the plugin is not installed.
  2. Check the plugin version number
    In the Installed plugins list, locate 'Bitbucket Server Integration' and note the Version column. Compare this version against 3.1.0.
    Affected if The installed version is 3.1.0 or earlier (e.g., 3.1.0, 3.0.9, etc.).
  3. Confirm OAuth consumer configuration exists
    Navigate to Manage Jenkins > Configure System > Bitbucket Server Integration section, or check the global configuration page for any configured OAuth consumers. Look for settings related to OAuth consumer or webhook configuration.
    Affected if No OAuth consumers are configured in Jenkins, the vulnerability is not reachable even with the vulnerable plugin version.
  4. Inspect OAuth consumer callback URLs
    If OAuth consumers are configured, examine each consumer's callback URL field. Look for URLs using non-standard schemes such as javascript:, data:, or other schemes that could contain script payloads.
    Affected if Any OAuth consumer has a callback URL with a non-http/https scheme (particularly javascript:, vbscript:, data:, or similar) containing what appears to be a malicious script payload.

A user is affected if they have Bitbucket Server Integration plugin version 3.1.0 or earlier AND have OAuth consumers configured with callback URLs that use non-standard URL schemes.

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 3.1.0
Interim mitigation

Upgrade the Jenkins Bitbucket Server Integration Plugin to version 3.1.1 or later, which implements proper URL scheme validation. Additionally, audit existing OAuth consumer configurations and restrict permissions for consumer creation to trusted users.

Recommended fix Moderate confidence

Bitbucket Server Integration plugin version 3.1.1 or later

  1. 1. Identify all Jenkins instances with the Bitbucket Server Integration plugin installed
  2. 2. Navigate to Manage Jenkins > Manage Plugins > Installed
  3. 3. Locate the Bitbucket Server Integration plugin and note the current version
  4. 4. If version is 3.1.0 or earlier, plan for upgrade
  5. 5. Before upgrading in production, test the new version in a non-production/staging environment
  6. 6. Backup Jenkins configuration and any relevant job configurations
  7. 7. Upgrade the Bitbucket Server Integration plugin to version 3.1.1 or later
  8. 8. Verify the plugin upgraded successfully and no errors appear in Jenkins logs
Caveat None documented for this security update; minor version upgrade should maintain compatibility

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

Fix this in Bitbucket Server Integration Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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