Bitbucket OauthApplication · Jenkins
CVE-2019-10460
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 · uneditedJenkins Bitbucket OAuth Plugin 0.9 and earlier stored credentials unencrypted in the global config.xml configuration file on the Jenkins master where they could be viewed by users with access to the master file system.
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 confidenceThe Jenkins Bitbucket OAuth Plugin versions 0.9 and earlier stored OAuth credentials (API tokens, client secrets, or similar authentication material) in plaintext within the global config.xml configuration file on the Jenkins master. Any user with file system access to the Jenkins controller could read these plaintext credentials.
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
<= 0.9CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Bitbucket OAuth Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed, or inspect the $JENKINS_HOME/plugins directory for a directory named 'bitbucket-oauth' or files with 'bitbucket-oauth' in the name.Affected if The plugin is present on the Jenkins instance.
-
Check the installed version of the pluginIn Manage Plugins > Installed, find the Bitbucket OAuth Plugin and note the version number. Alternatively, inspect the plugin's .jpi or .hpi file metadata in the plugins directory.Affected if The version is 0.9 or earlier.
-
Locate the global Jenkins configuration fileAccess the file $JENKINS_HOME/config.xml on the Jenkins controller file system.Affected if The config.xml file exists and is readable.
-
Inspect for Bitbucket OAuth credential storageOpen config.xml and search for sections related to 'bitbucket-oauth', 'bb-oauth', or 'com.cloudbees.jenkins.plugins.okato'. Look for XML elements containing 'secret', 'token', 'clientSecret', or 'apiToken'.Affected if The configuration contains Bitbucket OAuth settings with credentials stored in plaintext (visible as readable text rather than encrypted values).
You are affected if the Bitbucket OAuth Plugin version 0.9 or earlier is installed AND credentials are configured in config.xml, which would be visible in plaintext form to anyone with filesystem access.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade the Bitbucket OAuth Plugin to a version that encrypts stored credentials, then rotate all exposed credentials (API tokens, OAuth secrets) that may have been stored in the vulnerable configuration.
Fix this in Bitbucket Oauth
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10460 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10460 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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