REDHAT-BUG-839166: Low severity puppet Puppet vulnerability
From puppet labs: Puppet agents with certnames of IP addresses can be impersonated
This affects Puppet 2.6.16 and 2.7.17
If an authenticated host with a certname of an IP address changes IP addresses, and a second host assumes the first host's former IP address, the second host will be treated by the puppet master as the first one, giving the second host access to the first host's catalog. Note: This will not be fixed in Puppet versions prior to the forthcoming 3.x. Instead, with this announcement IP-based authentication in Puppet < 3.x is deprecated.
Resolved in Puppet 2.6.17, 2.7.18
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-839166?
The severity of REDHAT-BUG-839166 has not been explicitly categorized but it involves potential impersonation of Puppet agents which can lead to security risks.
How do I fix REDHAT-BUG-839166?
To fix REDHAT-BUG-839166, ensure that Puppet agents are configured to use fully qualified domain names instead of IP addresses for their certnames.
Which versions of Puppet are affected by REDHAT-BUG-839166?
Puppet versions 2.6.16 and 2.7.17 are affected by REDHAT-BUG-839166.
What is the impact of REDHAT-BUG-839166?
The impact of REDHAT-BUG-839166 is that an authenticated host can be impersonated if its certname is an IP address and the IP is reassigned to another host.
Is there a workaround for REDHAT-BUG-839166?
Yes, a workaround for REDHAT-BUG-839166 is to avoid using IP addresses as certnames and instead use unique and stable hostnames.