Skip to content

GHSA-pqj5-7r86-64fv CVE-2016-2785

Puppet Improper Access Control

Critical RubyGems
Severity
9.8 / 10
Critical · CVSS 3.1
Exploit chance (EPSS)
2.89%
Chance of exploitation in the next 30 days. Higher than 86.89% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-284 Improper Access Control
Fix
4.4.2
Upgrade puppet to this version or later

Description

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.

Affected versions

RubyGems

PackageVulnerableFixed in
puppet
>= 4.0.0, < 4.4.2
4.4.2

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

puppet RubyGems → 4.4.2

bundler
bundle update puppet # Gemfile: gem "puppet", ">= 4.4.2"

Severity breakdown

CVSS 3.1 9.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-mpmx-gm5v-q789
Puppet uses predictable filenames, allowing arbitrary file overwrite
Medium Also affects puppet
GHSA-9pvx-fwwh-w289
Puppet does not properly restrict access to node resources
Medium Also affects puppet
GHSA-qh3g-27jf-3j54
Puppet allows local users to modify the permissions of arbitrary files
Medium Also affects puppet
GHSA-8c56-v25w-f89c
Puppet arbitrary file overwrite
Medium Also affects puppet
GHSA-v58w-6xc2-w799
Puppet Denial of Service and Arbitrary File Write
Low Also affects puppet
GHSA-c4mc-49hq-q275
Puppet uses predictable filenames, allowing arbitrary file overwrite
Medium Also affects puppet
GHSA-6xxq-j39w-g3f6
Puppet Arbitrary Command Execution
Medium Also affects puppet
GHSA-77hg-g8cc-5r37
Puppet Privilege Escallation
Medium Also affects puppet
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor