CVE-2017-2294
HighSummary
Versions of Puppet Enterprise prior to 2016.4.5 and 2017.2.1 failed to mark MCollective server private keys as sensitive, which could lead to their logging and storage in PuppetDB.
Risk Assessment
The lack of marking keys as sensitive poses a risk of exposing confidential information, potentially leading to security breaches.
Recommendation
It is recommended to upgrade to Puppet Enterprise version 2016.4.5 or 2017.2.1 to ensure proper marking of keys as sensitive.
Other vulnerabilities in Puppet Enterprise
See all- CVE-2015-7330High
Puppet Enterprise 2015.3 before 2015.3.1 allows remote attackers to bypass a host whitelist protection mechanism by leveraging the Puppet communications protocol.
- CVE-2025-5459High
A user with specific node group editing permissions and a specially crafted class parameter could execute commands as root on the primary host. It affects Puppet Enterprise versions 2018.1.8 through 2023.8.3 and 2025.3, and has been resolved in versions 2023.8.4 and 2025.4.0.
Original NVD description (English source)
Versions of Puppet Enterprise prior to 2016.4.5 or 2017.2.1 failed to mark MCollective server private keys as sensitive (a feature added in Puppet 4.6), so key values could be logged and stored in PuppetDB. These releases use the sensitive data type to ensure this won't happen anymore.