Jenkins Configuration as Code Plugin has Insufficiently Protected Credentials

published 2018-06-26 8y ago modified 2026-06-17 4mo ago also GHSA-8486-h39x-cx2f , EUVD-2022-3100

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

A exposure of sensitive information vulnerability exists in Jenkins Configuration as Code Plugin 0.7-alpha and earlier in DataBoundConfigurator.java, Attribute.java, BaseConfigurator.java, ExtensionConfigurator.java that allows attackers with access to Jenkins log files to obtain the passwords configured using Configuration as Code Plugin.

Patch / fix

fixed in 1

maven io.jenkins:configuration-as-code 0.8-alpha

Is CVE-2018-1000610 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.90% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem	package	affected	fixed in
maven	io.jenkins:configuration-as-code	<0.8-alpha	0.8-alpha

Classification

Weakness

CWE-522 Insufficiently Protected Credentials

References

jenkins.io /security/advisory/2018-06-25/#SECURITY-929
web, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2018-1000610
advisory

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.