Jenkins eggplant-plugin Plugin stores credentials in plain text

published 2019-08-07 7y ago modified 2026-06-17 4mo ago also GHSA-xj63-95xc-jc4v , EUVD-2022-5806

cvss: 6.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.5%; EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits: 0; none known

Jenkins eggPlant Plugin 2.2 and earlier stores credentials unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the master file system.

Is CVE-2019-10385 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.48% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	6.5	CVSS:3.1/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.1	6.5	CVSS:3.1/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:eggplant-plugin	<=2.2	no fix listed

Affected products

Jenkins project Jenkins eggPlant Plugin

Classification

Weakness

CWE-522 Insufficiently Protected Credentials

References

jenkins.io /security/advisory/2019-08-07/#SECURITY-1430
web, vendor-advisory
openwall.com /lists/oss-security/2019/08/07/1
mailing-list, web, third-party-advisory
zerodayinitiative.com /advisories/ZDI-19-834/
third-party-advisory, vdb-entry
nvd.nist.gov /vuln/detail/CVE-2019-10385
advisory
zerodayinitiative.com /advisories/ZDI-19-834
web

Sources

Fencer Intel 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.