What is the severity of CVE-2017-2290?

CVE-2017-2290 has been rated as a high severity vulnerability due to the potential for privilege escalation by non-administrator users.

How does CVE-2017-2290 affect mcollective-puppet-agent?

CVE-2017-2290 allows non-administrator users on Windows to create executables that run with administrator privileges during the next 'mco puppet' execution.

Who is affected by CVE-2017-2290?

CVE-2017-2290 specifically affects Windows installations of mcollective-puppet-agent version 1.12.0, while Puppet Enterprise users are not impacted.

How do I fix CVE-2017-2290?

To fix CVE-2017-2290, upgrade the mcollective-puppet-agent to a version beyond 1.12.0 that addresses this vulnerability.

Is there a mitigation for CVE-2017-2290?

The best mitigation for CVE-2017-2290 is to ensure that users without administrative privileges are not allowed to execute the 'mco puppet' command.

Vulnerability/
CVE-2017-2290

critical

CWE

732

3/3/2017

5/8/2024

CVE-2017-2290

First published: Fri Mar 03 2017(Updated: )

On Windows installations of the mcollective-puppet-agent plugin, version 1.12.0, a non-administrator user can create an executable that will be executed with administrator privileges on the next "mco puppet" run. Puppet Enterprise users are not affected. This is resolved in mcollective-puppet-agent 1.12.1.

Credit: security@puppet.com

Affected Software	Affected Version	How to fix
Puppet MCollective	=1.12.0
Microsoft Windows

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-2290?
CVE-2017-2290 has been rated as a high severity vulnerability due to the potential for privilege escalation by non-administrator users.
How does CVE-2017-2290 affect mcollective-puppet-agent?
CVE-2017-2290 allows non-administrator users on Windows to create executables that run with administrator privileges during the next 'mco puppet' execution.
Who is affected by CVE-2017-2290?
CVE-2017-2290 specifically affects Windows installations of mcollective-puppet-agent version 1.12.0, while Puppet Enterprise users are not impacted.
How do I fix CVE-2017-2290?
To fix CVE-2017-2290, upgrade the mcollective-puppet-agent to a version beyond 1.12.0 that addresses this vulnerability.
Is there a mitigation for CVE-2017-2290?
The best mitigation for CVE-2017-2290 is to ensure that users without administrative privileges are not allowed to execute the 'mco puppet' command.

agent/type
agent/references
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/author
agent/weakness
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/puppet
canonical/puppet mcollective
version/puppet mcollective/1.12.0
vendor/microsoft
canonical/microsoft windows

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-2290?
CVE-2017-2290 has been rated as a high severity vulnerability due to the potential for privilege escalation by non-administrator users.
How does CVE-2017-2290 affect mcollective-puppet-agent?
CVE-2017-2290 allows non-administrator users on Windows to create executables that run with administrator privileges during the next 'mco puppet' execution.
Who is affected by CVE-2017-2290?
CVE-2017-2290 specifically affects Windows installations of mcollective-puppet-agent version 1.12.0, while Puppet Enterprise users are not impacted.
How do I fix CVE-2017-2290?
To fix CVE-2017-2290, upgrade the mcollective-puppet-agent to a version beyond 1.12.0 that addresses this vulnerability.
Is there a mitigation for CVE-2017-2290?
The best mitigation for CVE-2017-2290 is to ensure that users without administrative privileges are not allowed to execute the 'mco puppet' command.