CVE Vulnerabilities

CVE-2017-7890

Exposure of Sensitive Information to an Unauthorized Actor

Published: Aug 02, 2017 | Modified: May 04, 2018
CVSS 3.x
6.5
MEDIUM
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
CVSS 2.x
4.3 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
5.5 MODERATE
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Ubuntu
MEDIUM

The GIF decoding function gdImageCreateFromGifCtx in gd_gif_in.c in the GD Graphics Library (aka libgd), as used in PHP before 5.6.31 and 7.x before 7.1.7, does not zero colorMap arrays before use. A specially crafted GIF image could use the uninitialized tables to read ~700 bytes from the top of the stack, potentially disclosing sensitive information.

Weakness

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Affected Software

Name Vendor Start Version End Version
Php Php * 5.6.30 (including)
Php Php 7.0.0 (including) 7.0.0 (including)
Php Php 7.0.1 (including) 7.0.1 (including)
Php Php 7.0.2 (including) 7.0.2 (including)
Php Php 7.0.3 (including) 7.0.3 (including)
Php Php 7.0.4 (including) 7.0.4 (including)
Php Php 7.0.5 (including) 7.0.5 (including)
Php Php 7.0.6 (including) 7.0.6 (including)
Php Php 7.0.7 (including) 7.0.7 (including)
Php Php 7.0.8 (including) 7.0.8 (including)
Php Php 7.0.9 (including) 7.0.9 (including)
Php Php 7.0.10 (including) 7.0.10 (including)
Php Php 7.0.11 (including) 7.0.11 (including)
Php Php 7.0.12 (including) 7.0.12 (including)
Php Php 7.0.13 (including) 7.0.13 (including)
Php Php 7.0.14 (including) 7.0.14 (including)
Php Php 7.0.15 (including) 7.0.15 (including)
Php Php 7.0.16 (including) 7.0.16 (including)
Php Php 7.0.17 (including) 7.0.17 (including)
Php Php 7.0.18 (including) 7.0.18 (including)
Php Php 7.0.19 (including) 7.0.19 (including)
Php Php 7.0.20 (including) 7.0.20 (including)
Php Php 7.1.0 (including) 7.1.0 (including)
Php Php 7.1.1 (including) 7.1.1 (including)
Php Php 7.1.2 (including) 7.1.2 (including)
Php Php 7.1.3 (including) 7.1.3 (including)
Php Php 7.1.4 (including) 7.1.4 (including)
Php Php 7.1.5 (including) 7.1.5 (including)
Php Php 7.1.6 (including) 7.1.6 (including)
Red Hat Enterprise Linux 7 RedHat php-0:5.4.16-43.el7_4.1 *
Red Hat Software Collections for Red Hat Enterprise Linux 6 RedHat rh-php70-php-0:7.0.27-1.el6 *
Red Hat Software Collections for Red Hat Enterprise Linux 6.7 EUS RedHat rh-php70-php-0:7.0.27-1.el6 *
Red Hat Software Collections for Red Hat Enterprise Linux 7 RedHat rh-php70-php-0:7.0.27-1.el7 *
Red Hat Software Collections for Red Hat Enterprise Linux 7.3 EUS RedHat rh-php70-php-0:7.0.27-1.el7 *
Red Hat Software Collections for Red Hat Enterprise Linux 7.4 EUS RedHat rh-php70-php-0:7.0.27-1.el7 *
Red Hat Software Collections for Red Hat Enterprise Linux 7.5 EUS RedHat rh-php70-php-0:7.0.27-1.el7 *
Libgd2 Ubuntu devel *
Libgd2 Ubuntu trusty *
Libgd2 Ubuntu upstream *
Libgd2 Ubuntu xenial *
Libgd2 Ubuntu zesty *
Php5 Ubuntu upstream *
Php7.0 Ubuntu upstream *
Php7.1 Ubuntu upstream *

Extended Description

There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:

Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:

Information exposures can occur in different ways:

It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.

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