Jenkins Crowd 2 Integration Plugin stored credentials in plain text

published 2019-01-09 7y ago modified 2026-06-17 4mo ago also GHSA-cg6q-gp23-vwx8 , EUVD-2022-3572

cvss: 7.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits: 0; none known

An insufficiently protected credentials vulnerability exists in Jenkins Crowd 2 Integration Plugin 2.0.0 and earlier in CrowdSecurityRealm.java, CrowdConfigurationService.java that allows attackers with local file system access to obtain the credentials used to connect to Crowd 2.

Patch / fix

fixed in 1 links 1

maven org.jenkins-ci.plugins:crowd2 2.0.1

github.com/jenkinsci/crowd2-plugin@580be2a commit

Is CVE-2018-1000423 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

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

CVSS scores

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

Affected packages

ecosystem	package	affected	fixed in
maven	org.jenkins-ci.plugins:crowd2	<2.0.1	2.0.1

Classification

Weakness

CWE-522 Insufficiently Protected Credentials

References

github.com /jenkinsci/crowd2-plugin/commit/580be2a0dfb38d494420901f03555092b885a85f
web
securityfocus.com /bid/106532
vdb-entry, web, third-party-advisory
jenkins.io /security/advisory/2018-09-25/#SECURITY-1068
web, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2018-1000423
advisory
github.com /jenkinsci/crowd2-plugin
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.