CVE Vulnerabilities

CVE-2017-8291

Access of Resource Using Incompatible Type ('Type Confusion')

Published: Apr 27, 2017 | Modified: Oct 22, 2025
CVSS 3.x
7.8
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CVSS 2.x
6.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
7.3 IMPORTANT
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Ubuntu
HIGH
root.io logo minimus.io logo echo.ai logo

Artifex Ghostscript through 2017-04-26 allows -dSAFER bypass and remote command execution via .rsdparams type confusion with a /OutputFile (%pipe% substring in a crafted .eps document that is an input to the gs program, as exploited in the wild in April 2017.

Weakness

The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.

Affected Software

NameVendorStart VersionEnd Version
GhostscriptArtifex*9.21 (excluding)
Red Hat Enterprise Linux 6RedHatghostscript-0:8.70-23.el6_9.2*
Red Hat Enterprise Linux 7RedHatghostscript-0:9.07-20.el7_3.5*
GhostscriptUbuntudevel*
GhostscriptUbuntuesm-infra/xenial*
GhostscriptUbuntuprecise*
GhostscriptUbuntutrusty*
GhostscriptUbuntuxenial*
GhostscriptUbuntuyakkety*
GhostscriptUbuntuzesty*

Extended Description

When the product accesses the resource using an incompatible type, this could trigger logical errors because the resource does not have expected properties. In languages without memory safety, such as C and C++, type confusion can lead to out-of-bounds memory access. While this weakness is frequently associated with unions when parsing data with many different embedded object types in C, it can be present in any application that can interpret the same variable or memory location in multiple ways. This weakness is not unique to C and C++. For example, errors in PHP applications can be triggered by providing array parameters when scalars are expected, or vice versa. Languages such as Perl, which perform automatic conversion of a variable of one type when it is accessed as if it were another type, can also contain these issues.

References