CVE-2022-41137

Description

A flaw was found in the Apache Hive Metastore (HMS). This vulnerability allows remote code execution (RCE) via deserialization of arbitrary data when the SerializationUtilities#deserializeObjectWithTypeInformation method filters and fetches partitions without additional input validation. In real deployments, the vulnerability can be exploited only by authenticated users/clients who successfully establish a connection to the Metastore. From an API perspective, any code that calls the unsafe method may be vulnerable unless it performs additional rechecks on the input arguments.

Statement

The Metastore component is used to stores the structure information of tables and partitions in the warehouse, meaning this issue impacts mainly the integrity and availability of the system.

Mitigation

Any code that calls the unsafe method may be vulnerable unless it performs additional checks on the input arguments. Implementing additional validations on input arguments before passing them to the SerializationUtilities#deserializeObjectWithTypeInformation method might mitigate or decrease this risk.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score8.3N/AN/A
Attack VectorNetworkN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityLowN/AN/A
Integrity ImpactHighN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Application Data; Unexpected State

Attackers can modify unexpected objects or data that was assumed to be safe from modification. Deserialized data or code could be modified without using the provided accessor functions, or unexpected functions could be invoked.

Availability

Technical Impact: DoS: Resource Consumption (CPU)

If a function is making an assumption on when to terminate, based on a sentry in a string, it could easily never terminate.

Other

Technical Impact: Varies by Context

The consequences can vary widely, because it depends on which objects or methods are being deserialized, and how they are used. Making an assumption that the code in the deserialized object is valid is dangerous and can enable exploitation. One example is attackers using gadget chains to perform unauthorized actions, such as generating a shell.

Frequently Asked Questions

Want to get errata notifications? Sign up here.