CVE-2017-1000387
published 2018-01-26CVE-2017-1000387: Jenkins Build-Publisher plugin version 1.21 and earlier stores credentials to other Jenkins instances in the file…
PriorityP335high7.8CVSS 3.0
AVLACLPRLUINSUCHIHAH
EPSS
0.38%
31.1th percentile
Jenkins 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.
Affected
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| jenkins | all_versions_of_scp_publisher_plugin | — | — |
| jenkins | build-publisher | <= 1.21 | — |
| jenkins | build-publisher_plugin | — | — |
| jenkins | dependency_graph_viewer_plugin | — | — |
| jenkins | multijob_plugin | — | — |
| jenkins | scp_publisher_plugin | — | — |
| jenkins | urls_provided_by_global-build-stats_plugin | — | — |
CVSS provenance
nvdv3.07.8HIGHCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvdv2.02.1LOWAV:L/AC:L/Au:N/C:P/I:N/A:N
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Jenkins Build-Publisher plugin has Insufficiently Protected Credentials
osv·2022-05-13
CVE-2017-1000387 [HIGH] Jenkins Build-Publisher plugin has Insufficiently Protected Credentials
Jenkins Build-Publisher plugin has Insufficiently Protected Credentials
Jenkins 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. Build-Publisher Plugin 1.22 encrypts the credentials on disk, and only transmits their encrypted form to users viewing the configuration form.
GHSA
Jenkins Build-Publisher plugin has Insufficiently Protected Credentials
ghsa·2022-05-13
CVE-2017-1000387 [HIGH] CWE-522 Jenkins Build-Publisher plugin has Insufficiently Protected Credentials
Jenkins Build-Publisher plugin has Insufficiently Protected Credentials
Jenkins 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. Build-Publisher Plugin 1.22 encrypts the credentials on disk, and only transmits their encrypted form to users viewing the configuration form.
Jenkins
Jenkins Security Advisory 2017-10-23
vendor_jenkins·2017-10-23·CVSS 5.4
CVE-2017-1000386 [MEDIUM] Jenkins Security Advisory 2017-10-23
Title: Jenkins Security Advisory 2017-10-23
Jenkins Security Advisory 2017-10-23
This advisory announces vulnerabilities in these Jenkins plugins:
Active Choices (uno-choice)
Build-Publisher
Dependency Graph Viewer
global-build-stats
Multijob
SCP publisher
Description
Persisted Cross-Site Scripting vulnerability in Active Choices plugin
SECURITY-470 / CVE-2017-1000386
Active Choices plugin allowed users with Job/Configure permission to provide arbitrary HTML to be shown on the Build With Parameters page through the Active Choices Reactive Reference Parameter type.
This could include, for example, arbitrary JavaScript.
Active Choices now sanitizes the HTML inserted on the Build With Parameters page if and only if the sc
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2018-01-26
Published