Vulnerabilities
Misconfiguration
Runtime Security
Compliance
CVE Vulnerabilities

CVE-2016-2788

Improper Access Control

Published: Feb 13, 2017 | Modified: Jan 24, 2022
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
7.5 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
4.9 MODERATE
AV:N/AC:M/Au:S/C:P/I:P/A:N
RedHat/V3
6.1 MODERATE
CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:H/A:N
Ubuntu
MEDIUM
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2016-2788
CWEhttps://cwe.mitre.org/data/definitions/284.html

MCollective 2.7.0 and 2.8.x before 2.8.9, as used in Puppet Enterprise, allows remote attackers to execute arbitrary code via vectors related to the mco ping command.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Marionette_collective Puppet 2.7.0 (including) 2.7.0 (including)
Marionette_collective Puppet 2.8.0 (including) 2.8.0 (including)
Marionette_collective Puppet 2.8.1 (including) 2.8.1 (including)
Marionette_collective Puppet 2.8.2 (including) 2.8.2 (including)
Marionette_collective Puppet 2.8.3 (including) 2.8.3 (including)
Marionette_collective Puppet 2.8.4 (including) 2.8.4 (including)
Marionette_collective Puppet 2.8.5 (including) 2.8.5 (including)
Marionette_collective Puppet 2.8.6 (including) 2.8.6 (including)
Marionette_collective Puppet 2.8.7 (including) 2.8.7 (including)
Marionette_collective Puppet 2.8.8 (including) 2.8.8 (including)
Mcollective Ubuntu artful *
Mcollective Ubuntu precise *
Mcollective Ubuntu yakkety *
Mcollective Ubuntu zesty *

Extended Description

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:

Potential Mitigations

  • 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

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2024 Aqua Security Software Ltd.   Privacy Policy | Terms of Use