Build PublisherApplication · Jenkins
CVE-2017-1000387
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 Build-Publisher plugin version 1.21 and earlier stores credentials to other Jenkins instances in the file hudson.plugins.build_publisher.BuildPublisher.xml in the Jenkins master home directory. These credentials were stored unencrypted, allowing anyone with local file system access to access them. Additionally, the credentials were also transmitted in plain text as part of the configuration form. This could result in exposure of the credentials through browser extensions, cross-site scripting vulnerabilities, and similar situations.
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 Build-Publisher plugin versions 1.21 and earlier stores credentials used for authenticating to remote Jenkins instances in an XML configuration file (hudson.plugins.build_publisher.BuildPublisher.xml) without encryption. Additionally, these credentials are transmitted in plain text within the web configuration form, exposing them to browser-based attacks.
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
Build PublisherApplication
<= 1.21CVSS 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.0/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 Build-Publisher plugin is installedNavigate to Jenkins Manage Plugins > Installed tab, or check the plugins directory for the build-publisher pluginAffected if The Build-Publisher plugin is present in the Jenkins installation
-
Check the plugin versionView the plugin details in Jenkins Plugin Manager to confirm the version number is 1.21 or lowerAffected if The installed version is 1.21 or earlier (versions after 1.21 are not affected)
-
Locate the configuration fileFind the file named BuildPublisher.xml in the Jenkins home directory, typically under hudson.plugins.build_publisher/Affected if The configuration file exists and contains stored credentials
-
Inspect credentials for plaintext storageOpen the BuildPublisher.xml file and examine whether username and password fields contain unencrypted, plain text valuesAffected if Credentials in the XML file appear as plain text rather than encrypted or masked strings
-
Check web form for plaintext transmissionAccess the Build-Publisher configuration page via Jenkins UI (Manage Jenkins > Configure System > Build Publisher) and inspect the network traffic or form submission for unencrypted credential transmissionAffected if Credentials are submitted or displayed in plain text within the web configuration interface
A user is affected if the Build-Publisher plugin version is 1.21 or earlier AND the XML configuration file contains plaintext credentials or the web form transmits credentials without encryption.
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 dataUpdate the Build-Publisher plugin to a version after 1.21 that implements encrypted credential storage and secure transmission. Immediately rotate any credentials that may have been stored using the vulnerable plugin.
Fix this in Build Publisher
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000387 — 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-2017-1000387 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