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.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Puppet | Puppet | 4.0.0 (including) | 4.0.0 (including) |
| Puppet | Puppet | 4.0.0-rc1 (including) | 4.0.0-rc1 (including) |
| Puppet | Puppet | 4.0.0-rc2 (including) | 4.0.0-rc2 (including) |
| Puppet | Puppet | 4.0.0-rc3 (including) | 4.0.0-rc3 (including) |
| Puppet | Puppet | 4.1.0 (including) | 4.1.0 (including) |
| Puppet | Puppet | 4.2.0 (including) | 4.2.0 (including) |
| Puppet | Puppet | 4.2.1 (including) | 4.2.1 (including) |
| Puppet | Puppet | 4.2.2 (including) | 4.2.2 (including) |
| Puppet | Puppet | 4.2.3 (including) | 4.2.3 (including) |
| Puppet | Puppet | 4.3.0 (including) | 4.3.0 (including) |
| Puppet | Puppet | 4.3.1 (including) | 4.3.1 (including) |
| Puppet | Puppet | 4.3.2 (including) | 4.3.2 (including) |
| Puppet | Puppet | 4.4.0 (including) | 4.4.0 (including) |
| Puppet | Puppet | 4.4.1 (including) | 4.4.1 (including) |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: