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 cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Puppet Puppet | =4.0.0 | |
Puppet Puppet | =4.0.0-rc1 | |
Puppet Puppet | =4.0.0-rc2 | |
Puppet Puppet | =4.0.0-rc3 | |
Puppet Puppet | =4.1.0 | |
Puppet Puppet | =4.2.0 | |
Puppet Puppet | =4.2.1 | |
Puppet Puppet | =4.2.2 | |
Puppet Puppet | =4.2.3 | |
Puppet Puppet | =4.3.0 | |
Puppet Puppet | =4.3.1 | |
Puppet Puppet | =4.3.2 | |
Puppet Puppet | =4.4.0 | |
Puppet Puppet | =4.4.1 | |
Puppet Puppet Server | =2.0.0 | |
Puppet Puppet Server | =2.1.0 | |
Puppet Puppet Server | =2.1.1 | |
Puppet Puppet Server | =2.1.2 | |
Puppet Puppet Server | =2.2.0 | |
Puppet Puppet Server | =2.3.0 | |
Puppet Puppet Server | =2.3.1 | |
Puppet Puppet Agent | =1.4.1 | |
rubygems/puppet | >=4.0.0<4.4.2 | 4.4.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.