Vulnerabilities · 2017 · Puppet
CVE-2017-2298
Puppet Mcollective-sshkey-security vulnerability
The mcollective-sshkey-security plugin before 0.5.1 for Puppet uses a server-specified identifier as part of a path where a file is written. A compromised server could use this to write a file to an arbitrary location on the client with the filename appended with the string "_pub.pem".
Affected products
Mcollective-sshkey-security. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Puppet Mcollective-sshkey-security runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- puppet.com/security/cve/cve-2017-2298 · Mitigation
- github.com/puppetlabs/mcollective-sshkey-security/blob/0.5.1/CHANGELOG.md · Third Party Advisory
- github.com/puppetlabs/mcollective-sshkey-security/commit/3388a3109f4fb1c69fa8505e991bf59ca · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2017-2298
- cve.org/CVERecord?id=CVE-2017-2298
More vulnerabilities in Puppet products
CVE-2025-5459CVE-2023-5309CVE-2023-5255CVE-2023-5214CVE-2023-2530CVE-2023-1894CVE-2022-3276CVE-2022-3275All 128
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.