CVE Vulnerabilities

CVE-2023-26359

Deserialization of Untrusted Data

Published: Mar 23, 2023 | Modified: Mar 28, 2023
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

Adobe ColdFusion versions 2018 Update 15 (and earlier) and 2021 Update 5 (and earlier) are affected by a Deserialization of Untrusted Data vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue does not require user interaction.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Coldfusion Adobe 2018 2018
Coldfusion Adobe 2018 2018
Coldfusion Adobe 2018 2018
Coldfusion Adobe 2018 2018
Coldfusion Adobe 2018 2018
Coldfusion Adobe 2018 2018
Coldfusion Adobe 2018 2018
Coldfusion Adobe 2018 2018
Coldfusion Adobe 2018 2018
Coldfusion Adobe 2018 2018
Coldfusion Adobe 2018 2018
Coldfusion Adobe 2018 2018
Coldfusion Adobe 2018 2018
Coldfusion Adobe 2018 2018
Coldfusion Adobe 2018 2018
Coldfusion Adobe 2018 2018
Coldfusion Adobe 2021 2021
Coldfusion Adobe 2021 2021
Coldfusion Adobe 2021 2021
Coldfusion Adobe 2021 2021
Coldfusion Adobe 2021 2021
Coldfusion Adobe 2021 2021

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