CVE Vulnerabilities

CVE-2019-8169

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

Published: Oct 17, 2019 | Modified: Sep 08, 2021
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.1/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
RedHat/V3
Ubuntu

Adobe Acrobat and Reader versions , 2019.012.20040 and earlier, 2017.011.30148 and earlier, 2017.011.30148 and earlier, 2015.006.30503 and earlier, and 2015.006.30503 and earlier have a type confusion vulnerability. Successful exploitation could lead to arbitrary code execution .

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

Name Vendor Start Version End Version
Acrobat_dc Adobe 15.006.30060 (including) 15.006.30504 (excluding)
Acrobat_dc Adobe 15.008.20082 (including) 19.021.20047 (excluding)
Acrobat_dc Adobe 17.011.30059 (including) 17.011.30150 (excluding)
Acrobat_reader_dc Adobe 15.006.30060 (including) 15.006.30504 (excluding)
Acrobat_reader_dc Adobe 15.008.20082 (including) 19.021.20047 (excluding)
Acrobat_reader_dc Adobe 17.011.30059 (including) 17.011.30150 (excluding)

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