puppet vulnerabilities
Puppet, an automated administrative engine for your Linux, Unix, and Windows systems, performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.
- Registry
- RubyGems
- Latest
- 8.10.0
- License
- Apache-2.0
23 known advisories
The latest version, 8.10.0, is not affected by any of them. Projects on older versions may be.
bundle update --conservative puppet # Gemfile: '>= 8.10.0'Is your project on an affected puppet?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for puppet
Puppet does not properly restrict access to node resources
- Affected
- >=2.6.0 <2.6.4
- Fixed in
- 2.6.4
Puppet uses predictable filenames, allowing arbitrary file overwrite
- Affected
- >=2.7.0 <2.7.5 · <2.6.11
- Fixed in
- 2.6.11, 2.7.5
Puppet arbitrary file overwrite
- Affected
- >=2.7.0 <2.7.5 · <2.6.11
- Fixed in
- 2.6.11, 2.7.5
Puppet allows local users to modify the permissions of arbitrary files
- Affected
- >=2.7.0 <2.7.5 · <2.6.11
- Fixed in
- 2.6.11, 2.7.5
Puppet Arbitrary Command Execution
- Affected
- >=2.6.0 <2.6.15 · >=2.7.0 <2.7.13
- Fixed in
- 2.6.15, 2.7.13
Puppet uses predictable filenames, allowing arbitrary file overwrite
- Affected
- >=2.6 <2.6.15 · >=2.7 <2.7.13
- Fixed in
- 2.6.15, 2.7.13
Puppet Denial of Service and Arbitrary File Write
- Affected
- >=2.6.0 <2.6.15 · >=2.7.0 <2.7.13
- Fixed in
- 2.6.15, 2.7.13
Puppet Privilege Escallation
- Affected
- >=2.6 <2.6.14 · >=2.7 <2.7.11
- Fixed in
- 2.6.14, 2.7.11
Tarball permission preservation in puppet
- Affected
- <4.10.10 · >=5.0.0 <5.3.4
- Fixed in
- 4.10.10, 5.3.4
Puppet Improper Access Control
- Affected
- >=4.0.0 <4.4.2
- Fixed in
- 4.4.2
Puppet arbitrary files overwrite via a symlink attack
- Affected
- >=0.24.0 <0.24.9 · >=0.25.0 <0.25.2
- Fixed in
- 0.24.9, 0.25.2
Silent Configuration Failure in Puppet Agent
- Affected
- >=7.0.0 <7.12.1 · <6.25.1
- Fixed in
- 6.25.1, 7.12.1
Unsafe HTTP Redirect in Puppet Agent and Puppet Server
- Affected
- >=7.0.0 <7.12.1 · <6.25.1
- Fixed in
- 6.25.1, 7.12.1
Improper Certificate Validation in Puppet
- Affected
- >=6.0.0 <6.13.0 · <5.5.19
- Fixed in
- 5.5.19, 6.13.0
Puppet allows local users to overwrite arbitrary files via a symlink attack
- Affected
- >=2.7.1 <2.7.13
- Fixed in
- 2.7.13
Puppet supports use of IP addresses in certnames without warning of potential risks
- Affected
- <2.7.18
- Fixed in
- 2.7.18
Puppet Improper Input Validation vulnerability
- Affected
- >=2.7.0 <2.7.21 · >=3.1.0 <3.1.1
- Fixed in
- 2.7.21, 3.1.1
Puppet Improper Input Validation vulnerability
- Affected
- >=2.7.0 <2.7.22 · >=3.2.0 <3.2.2
- Fixed in
- 2.7.22, 3.2.2
Puppet allows remote attackers to execute arbitrary Ruby programs from the master via the resource_type service
- Affected
- >=2.7.0 <2.7.23 · >=3.2.0 <3.2.4
- Fixed in
- 2.7.23, 3.2.4
Pupper does not properly restrict characters in Common Name field of Certificate Signing Request
- Affected
- <2.6.17 · >=2.7.0 <2.7.18
- Fixed in
- 2.6.17, 2.7.18
Puppet allows local users to obtain sensitive configuration information
- Affected
- >=2.7.0 <2.7.18
- Fixed in
- 2.7.18
Puppet vulnerable to Path Traversal
- Affected
- <2.6.17 · >=2.7.0 <2.7.18
- Fixed in
- 2.6.17, 2.7.18
facter, hiera, mcollective-client, and puppet affected by untrusted search path vulnerability
- Affected
- <2.7.26 · >=3.0.0 <3.6.2
- Fixed in
- 2.7.26, 3.6.2
Is your puppet version vulnerable?
- puppet 8.10No known advisories in 8.10.0
- puppet 8.9No known advisories in 8.9.0
- puppet 8.8No known advisories in 8.8.1
- puppet 8.7No known advisories in 8.7.0
- puppet 8.6No known advisories in 8.6.0
- puppet 8.5No known advisories in 8.5.1
- puppet 7.34No known advisories in 7.34.0
- puppet 7.33No known advisories in 7.33.0
- puppet 7.32No known advisories in 7.32.1
- puppet 7.31No known advisories in 7.31.0
- puppet 7.30No known advisories in 7.30.0
- puppet 7.29No known advisories in 7.29.1
- puppet 6.29No known advisories in 6.29.0
- puppet 6.28No known advisories in 6.28.0
- puppet 6.27No known advisories in 6.27.0
- puppet 6.26No known advisories in 6.26.0
- puppet 6.25No known advisories in 6.25.1
- puppet 6.242 advisories in 6.24.0
Which of your client projects still run an old puppet?
NPMscan reads the Gemfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other RubyGems packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the RubyGems registry.