Cleartext Storage of Sensitive Information for Puppet Resource API
Perforce Puppet Core · Perforce Puppet Enterprise
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Perforce Puppet Core |
|
|
| Perforce Puppet Enterprise |
|
|
Perforce Puppet Core · Perforce Puppet Enterprise
| Product | Affected | Fixed in |
|---|---|---|
| Perforce Puppet Core |
|
|
| Perforce Puppet Enterprise |
|
|
Puppet resource_api (shipped in Puppet Core 8.x and Puppet Enterprise 2023.8.x and 2025.x) does not preserve the sensitive flag on parameters defined via the resource-api, causing values such as passwords to be stored in cleartext in the agent's local transaction state cache. Affected versions of the resource_api module include all versions between 1.5.0 - 1.9.1 and 2.0.0 The issue was fixed in puppet resource_api 1.9.2 and 2.0.1 released with Puppet Core 8.20.0 and PE 2023.8.10 & PE 2025.11.0.
From the CVE record · Perforce
Puppet resource_api fails to preserve the sensitive flag on parameters it defines, causing values such as passwords to be stored in cleartext in the agent's local transaction state cache. Someone able to read that local cache could see those values; the input does not describe a network attack or required user interaction.
Operators of Puppet Core 8.x or Puppet Enterprise 2023.8.x or 2025.x should check for resource_api versions 1.5.0–1.9.1 or 2.0.0.