First published: Fri Jun 10 2016(Updated: )
Puppet Server before 2.3.2 and Ruby puppetmaster in Puppet 4.x before 4.4.2 and in Puppet Agent before 1.4.2 might allow remote attackers to bypass intended auth.conf access restrictions by leveraging incorrect URL decoding.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
rubygems/puppet | <2.3.2 | |
rubygems/puppet | >=4.0.0<4.4.2 | 4.4.2 |
Puppet | =4.0.0 | |
Puppet | =4.0.0-rc1 | |
Puppet | =4.0.0-rc2 | |
Puppet | =4.0.0-rc3 | |
Puppet | =4.1.0 | |
Puppet | =4.2.0 | |
Puppet | =4.2.1 | |
Puppet | =4.2.2 | |
Puppet | =4.2.3 | |
Puppet | =4.3.0 | |
Puppet | =4.3.1 | |
Puppet | =4.3.2 | |
Puppet | =4.4.0 | |
Puppet | =4.4.1 | |
Puppet Server | =2.0.0 | |
Puppet Server | =2.1.0 | |
Puppet Server | =2.1.1 | |
Puppet Server | =2.1.2 | |
Puppet Server | =2.2.0 | |
Puppet Server | =2.3.0 | |
Puppet Server | =2.3.1 | |
Puppet | =1.4.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-2785 has a medium severity rating due to its potential to allow unauthorized access by bypassing access restrictions.
To fix CVE-2016-2785, upgrade Puppet Server to version 2.3.2 or later, or Puppet 4.x to version 4.4.2 or later.
CVE-2016-2785 affects Puppet Server versions before 2.3.2 and Puppet versions 4.x before 4.4.2.
Yes, CVE-2016-2785 can be exploited by remote attackers to bypass access controls.
CVE-2016-2785 primarily impacts the auth.conf access restrictions in Puppet Server and Ruby puppetmaster.