dbcve.org
Bitbucket OauthApplication · Jenkins

CVE-2023-24427

CRITICAL · 9.8 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to after 0.13 or later.
See remediation →
100/100
Remediation priority · Urgent
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 OAuth Plugin 0.12 and earlier does not invalidate the previous session on login.

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 · moderate confidence

The Jenkins Bitbucket OAuth Plugin 0.12 and earlier fails to invalidate the previous session upon successful login, allowing session fixation attacks where an attacker who has obtained a valid session ID can maintain access after the legitimate user authenticates via OAuth.

MitigationUpgrade the Bitbucket OAuth Plugin to version 0.13 or later, which implements proper session invalidation on login.

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 OauthApplication
Affected:<= 0.13

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
High
Availability
High

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

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. Identify Bitbucket OAuth Plugin installation
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Bitbucket OAuth' or 'bitbucket-oauth' to confirm the plugin is installed
    Affected if plugin is not installed (not affected)
  2. Determine installed plugin version
    In the Installed plugins list, locate the Bitbucket OAuth Plugin and note the Version column. If using CLI, run: jenkins-plugin-cli --list-plugins | grep -i bitbucket-oauth or check $JENKINS_HOME/plugins/ for the plugin directory
    Affected if version is 0.12 or earlier (vulnerable if OAuth is configured)
  3. Verify OAuth authentication is configured
    Navigate to Jenkins > Manage Jenkins > Configure Global Security > Security Realms and check if 'Bitbucket OAuth' is selected as the security realm, or inspect the configuration XML at $JENKINS_HOME/config.xml for <securityRealm> containing 'bitbucket-oauth'
    Affected if OAuth is not configured as the authentication method (not affected)
  4. Confirm session handling behavior
    Review the plugin version against the affected range. The vulnerability exists in versions 0.12 and earlier where session invalidation is not performed after successful OAuth login
    Affected if plugin version <= 0.13 AND OAuth is configured as the security realm

User is affected if the Bitbucket OAuth Plugin version is 0.12 or earlier AND the plugin is actively configured as the authentication method in Jenkins security settings

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

Upgrade the Bitbucket OAuth Plugin to version 0.13 or later, which implements proper session invalidation on login.

Recommended fix High confidence

Bitbucket OAuth Plugin version 0.13 or later

  1. Navigate to Jenkins Manage Plugins page
  2. Go to the 'Available' tab and search for 'Bitbucket OAuth Plugin'
  3. If the plugin is already installed, go to 'Installed' tab and find Bitbucket OAuth Plugin
  4. Click 'Update' or 'Install' to upgrade to the latest version
  5. Restart Jenkins if required to complete the installation
  6. Alternatively, manually download the .hpi file from Jenkins wiki or Jenkins update center and upload via 'Advanced' tab in plugin manager
Caveat Review plugin release notes for any configuration or compatibility changes with Bitbucket Cloud/Server

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

Fix this in Bitbucket Oauth Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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