CVE Vulnerabilities

CVE-2022-1471

Deserialization of Untrusted Data

Published: Dec 01, 2022 | Modified: Jun 21, 2024
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
RedHat/V2
RedHat/V3
9.8 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM

SnakeYamls Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYamls SafeConsturctor when parsing untrusted content to restrict deserialization. We recommend upgrading to version 2.0 and beyond.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Snakeyaml Snakeyaml_project * 2.0 (excluding)
AMQ Clients RedHat snakeyaml *
EAP 7.4.10 release RedHat snakeyaml *
OpenShift Developer Tools and Services for OCP 4.11 RedHat jenkins-2-plugins-0:4.11.1683009941-1.el8 *
OpenShift Developer Tools and Services for OCP 4.11 RedHat jenkins-2-plugins-0:4.11.1698299029-1.el8 *
OpenShift Developer Tools and Services for OCP 4.11 RedHat jenkins-2-plugins-0:4.11.1706516946-1.el8 *
Red Hat AMQ Streams 2.5.0 RedHat *
Red Hat build of Eclipse Vert.x 4.3.4 RedHat snakeyaml *
Red Hat build of Quarkus RedHat *
Red Hat build of Quarkus 2.7.7 RedHat snakeyaml *
Red Hat Enterprise Linux 8 RedHat prometheus-jmx-exporter-0:0.12.0-9.el8_7 *
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8 RedHat eap7-snakeyaml-0:1.33.0-2.SP1_redhat_00001.1.el8eap *
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 9 RedHat eap7-snakeyaml-0:1.33.0-2.SP1_redhat_00001.1.el9eap *
Red Hat JBoss Enterprise Application Platform 7.4 on RHEL 7 RedHat eap7-snakeyaml-0:1.33.0-2.SP1_redhat_00001.1.el7eap *
Red Hat OpenShift Container Platform 4.10 RedHat jenkins-2-plugins-0:4.10.1675407676-1.el8 *
Red Hat OpenShift Container Platform 4.9 RedHat jenkins-2-plugins-0:4.9.1675668922-1.el8 *
Red Hat Satellite 6.13 for RHEL 8 RedHat candlepin-0:4.2.13-1.el8sat *
Red Hat Single Sign-On 7 RedHat snakeyaml *
Red Hat Single Sign-On 7.6 for RHEL 7 RedHat rh-sso7-keycloak-0:18.0.6-1.redhat_00001.1.el7sso *
Red Hat Single Sign-On 7.6 for RHEL 8 RedHat rh-sso7-keycloak-0:18.0.6-1.redhat_00001.1.el8sso *
Red Hat Single Sign-On 7.6 for RHEL 9 RedHat rh-sso7-keycloak-0:18.0.6-1.redhat_00001.1.el9sso *
Red Hat support for Spring Boot 2.7.13 RedHat snakeyaml *
RHEL-7 based Middleware Containers RedHat openjdk/openjdk-11-rhel7:1.17-1 *
RHEL-7 based Middleware Containers RedHat redhat-openjdk-18/openjdk18-openshift:1.17-1 *
RHEL-8 based Middleware Containers RedHat ubi8/openjdk-11:1.14-11 *
RHEL-8 based Middleware Containers RedHat ubi8/openjdk-11-runtime:1.14-11 *
RHEL-8 based Middleware Containers RedHat ubi8/openjdk-17:1.14-9 *
RHEL-8 based Middleware Containers RedHat ubi8/openjdk-17-runtime:1.14-8 *
RHEL-8 based Middleware Containers RedHat ubi8/openjdk-8:1.14-12 *
RHEL-8 based Middleware Containers RedHat ubi8/openjdk-8-runtime:1.14-10 *
RHEL-8 based Middleware Containers RedHat rh-sso-7/sso76-openshift-rhel8:7.6-20 *
RHPAM 7.13.5 async RedHat snakeyaml *
Snakeyaml Ubuntu bionic *
Snakeyaml Ubuntu kinetic *
Snakeyaml Ubuntu lunar *
Snakeyaml Ubuntu mantic *
Snakeyaml Ubuntu trusty *
Snakeyaml Ubuntu trusty/esm *
Snakeyaml Ubuntu xenial *

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