CVE-2016-2787
First published: Mon Feb 13 2017(Updated: )
The Puppet Communications Protocol in Puppet Enterprise 2015.3.x before 2015.3.3 does not properly validate certificates for the broker node, which allows remote non-whitelisted hosts to prevent runs from triggering via unspecified vectors.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Puppet Enterprise | =2015.3.2 | |
| Puppet Enterprise | =2015.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-2787?
CVE-2016-2787 is classified as a medium severity vulnerability.
How do I fix CVE-2016-2787?
To fix CVE-2016-2787, upgrade Puppet Enterprise to version 2015.3.3 or later.
What is affected by CVE-2016-2787?
CVE-2016-2787 affects Puppet Enterprise versions 2015.3.x prior to 2015.3.3.
What does CVE-2016-2787 exploit?
CVE-2016-2787 exploits improper certificate validation in the Puppet Communications Protocol.
What risks are associated with CVE-2016-2787?
The risks associated with CVE-2016-2787 include unauthorized access by remote hosts, potentially disrupting Puppet operations.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/severity
- agent/references
- agent/author
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/description
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/puppet
- canonical/puppet enterprise
- version/puppet enterprise/2015.3.2
- vendor/puppetlabs
- version/puppet enterprise/2015.3