Skip to content
Fencer Vulns
medium 6.5

CVE-2018-1000601 json

Exposure of Sensitive Information to an Unauthorized Actor in Jenkins SSH Credentials Plugin

published 2018-06-26 8 y ago modified 2026-06-17 4 mo ago also GHSA-cwcf-5m5w-mq2w , EUVD-2022-3646

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
0
none known

Summary

A arbitrary file read vulnerability exists in Jenkins SSH Credentials Plugin 1.13 and earlier in BasicSSHUserPrivateKey.java that allows attackers with a Jenkins account and the permission to configure credential bindings to read arbitrary files from the Jenkins master file system.

Patch / fix

  • maven org.jenkins-ci.plugins:ssh-credentials 1.14
  • maven org.jenkins-ci.plugins:credentials 2.1.17

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-1000601 updated cvss 6.5

jenkins-plugin-ssh-credentials: Arbitrary file read vulnerability in SSH Credentials Plugin with Credentials Binding Plugin (SECURITY-440)

  • Red Hat OpenShift Enterprise 3 jenkins-plugin-ssh-credentials
    affected: no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.01% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.plugins:ssh-credentials
<1.14
1.14
maven org.jenkins-ci.plugins:credentials
<2.1.17
2.1.17

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.