Bitbucket ApproveApplication · Jenkins
CVE-2019-1003057
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 Approve Plugin stores credentials unencrypted in its global configuration file on the Jenkins master where they can 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 Approve Plugin stores credentials unencrypted in plaintext within its global configuration file on the Jenkins master. Users with access to the Jenkins master file system can directly read these stored credentials, exposing them to unauthorized parties.
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 ApproveApplication
all versionsCVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Identify if Bitbucket Approve Plugin is installedNavigate to the Jenkins web UI, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Bitbucket Approve', or list installed plugins via the Jenkins CLI or file system in the plugins directoryAffected if The Bitbucket Approve Plugin appears in the list of installed plugins
-
Locate the plugin global configuration fileIn the Jenkins home directory, look for the Bitbucket Approve Plugin configuration file in the plugin's directory or in the Jenkins configuration root where global plugin configs are storedAffected if A configuration file for the Bitbucket Approve Plugin exists in the Jenkins home directory
-
Examine the configuration file for stored credentialsOpen the configuration file using a text editor or command line tool and inspect its contents for credential fields - look for any username, password, token, or secret fields and verify whether they appear in plaintext rather than encrypted or masked formatAffected if The configuration file contains credential values in plaintext (readable text strings) rather than being masked, encrypted, or referenced as credential IDs
A user is affected if the Bitbucket Approve Plugin is installed and its global configuration file contains plaintext credentials that can be directly read from the file system.
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 to a patched version of the Bitbucket Approve Plugin that implements proper credential encryption using Jenkins' built-in credential storage API. Immediately rotate any credentials that may have been exposed through this vulnerability.
Fix this in Bitbucket Approve
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,768.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003057 — 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-1003057 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