CVE Vulnerabilities

CVE-2019-7361

Deserialization of Untrusted Data

Published: Apr 09, 2019 | Modified: Apr 11, 2019
CVSS 3.x
7.8
HIGH
Source:
NVD
CVSS:3.0/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
Ubuntu

An attacker may convince a victim to open a malicious action micro (.actm) file that has serialized data, which may trigger a code execution in Autodesk Advance Steel 2018, Autodesk AutoCAD 2018, Autodesk AutoCAD Architecture 2018, Autodesk AutoCAD Electrical 2018, Autodesk AutoCAD Map 3D 2018, Autodesk AutoCAD Mechanical 2018, Autodesk AutoCAD MEP 2018, Autodesk AutoCAD P&ID 2018, Autodesk AutoCAD Plant 3D 2018, Autodesk AutoCAD LT 2018, and Autodesk Civil 3D 2018.

Weakness

The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid.

Affected Software

Name Vendor Start Version End Version
Advance_steel Autodesk 2018 (including) 2018 (including)
Autocad Autodesk 2018 (including) 2018 (including)
Autocad_architecture Autodesk 2018 (including) 2018 (including)
Autocad_electrical Autodesk 2018 (including) 2018 (including)
Autocad_lt Autodesk 2018 (including) 2018 (including)
Autocad_map_3d Autodesk 2018 (including) 2018 (including)
Autocad_mechanical Autodesk 2018 (including) 2018 (including)
Autocad_mep Autodesk 2018 (including) 2018 (including)
Autocad_p&id Autodesk 2018 (including) 2018 (including)
Autocad_plant_3d Autodesk 2018 (including) 2018 (including)
Civil_3d Autodesk 2018 (including) 2018 (including)

Extended Description

It is often convenient to serialize objects for communication or to save them for later use. However, deserialized data or code can often be modified without using the provided accessor functions if it does not use cryptography to protect itself. Furthermore, any cryptography would still be client-side security – which is a dangerous security assumption. Data that is untrusted can not be trusted to be well-formed. When developers place no restrictions on “gadget chains,” or series of instances and method invocations that can self-execute during the deserialization process (i.e., before the object is returned to the caller), it is sometimes possible for attackers to leverage them to perform unauthorized actions, like generating a shell.

Potential Mitigations

  • Make fields transient to protect them from deserialization.
  • An attempt to serialize and then deserialize a class containing transient fields will result in NULLs where the transient data should be. This is an excellent way to prevent time, environment-based, or sensitive variables from being carried over and used improperly.

References