When using the cd4pe::root_configuration task to configure a Continuous Delivery for PE installation, the root user’s username and password…

published 2019-12-11 6y ago modified 2026-06-17 4mo ago also EUVD-2019-2489

cvss: 6.5; version 3.1, 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

When using the cd4pe::root_configuration task to configure a Continuous Delivery for PE installation, the root user’s username and password were exposed in the job’s Job Details pane in the PE console. These issues have been resolved in version 1.2.1 of the puppetlabs/cd4pe module.

Patch / fix

fixed in 1

puppet continuous_delivery 1.2.1

Is CVE-2019-10695 in your stack? 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.88% 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.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

Affected products

n/a Continuous Delivery for Puppet Enterprise (CD4PE)

Classification

Weakness

CWE-532 Insertion of Sensitive Information into Log File

References

puppet.com /security/cve/CVE-2019-10695
vendor-advisory

Sources

CVE List CVE-2019-10695
NVD CVE-2019-10695

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.