CVE Vulnerabilities

CVE-2016-5239

Improper Access Control

Published: Mar 15, 2017 | Modified: Apr 20, 2025
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
5.1 MODERATE
AV:N/AC:H/Au:N/C:P/I:P/A:P
RedHat/V3
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

The gnuplot delegate functionality in ImageMagick before 6.9.4-0 and GraphicsMagick allows remote attackers to execute arbitrary commands via unspecified vectors.

Weakness

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

Affected Software

NameVendorStart VersionEnd Version
ImagemagickImagemagick*6.9.3-9 (including)
Red Hat Enterprise Linux 6RedHatImageMagick-0:6.7.2.7-5.el6_8*
Red Hat Enterprise Linux 7RedHatImageMagick-0:6.7.8.9-15.el7_2*
GraphicsmagickUbuntuesm-apps/xenial*
GraphicsmagickUbuntuesm-infra-legacy/trusty*
GraphicsmagickUbuntuprecise*
GraphicsmagickUbuntutrusty*
GraphicsmagickUbuntutrusty/esm*
GraphicsmagickUbuntuupstream*
GraphicsmagickUbuntuwily*
GraphicsmagickUbuntuxenial*
ImagemagickUbuntuartful*
ImagemagickUbuntubionic*
ImagemagickUbuntucosmic*
ImagemagickUbuntudevel*
ImagemagickUbuntuesm-infra-legacy/trusty*
ImagemagickUbuntuesm-infra/bionic*
ImagemagickUbuntuesm-infra/xenial*
ImagemagickUbuntuprecise*
ImagemagickUbuntutrusty*
ImagemagickUbuntutrusty/esm*
ImagemagickUbuntuupstream*
ImagemagickUbuntuwily*
ImagemagickUbuntuxenial*
ImagemagickUbuntuyakkety*
ImagemagickUbuntuzesty*

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