CVE-2021-28131 Vulnerability Analysis & Exploit Details

CVE-2021-28131
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2021-28131 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2021-28131 Details

Status: Modified

Last updated: 🕠 21 Nov 2024, 05:59 UTC
Originally published on: 🕙 22 Jul 2021, 10:15 UTC

Time between publication and last update: 1217 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2021-28131 Vulnerability Summary

CVE-2021-28131: Impala sessions use a 16 byte secret to verify that the session is not being hijacked by another user. However, these secrets appear in the Impala logs, therefore Impala users with access to the logs can use another authenticated user's sessions with specially constructed requests. This means the attacker is able to execute statements for which they don't have the necessary privileges otherwise. Impala deployments with Apache Sentry or Apache Ranger authorization enabled may be vulnerable to privilege escalation if an authenticated attacker is able to hijack a session or query from another authenticated user with privileges not assigned to the attacker. Impala deployments with audit logging enabled may be vulnerable to incorrect audit logging as a user could undertake actions that were logged under the name of a different authenticated user. Constructing an attack requires a high degree of technical sophistication and access to the Impala system as an authenticated user. Mitigation: If an Impala deployment uses Apache Sentry, Apache Ranger or audit logging, then users should upgrade to a version of Impala with the fix for IMPALA-10600. The Impala 4.0 release includes this fix. This hides session secrets from the logs to eliminate the risk of any attack using this mechanism. In lieu of an upgrade, restricting access to logs that expose secrets will reduce the risk of an attack. Restricting access to the Impala deployment to trusted users will also reduce the risk of an attack. Log redaction techniques can be used to redact secrets from the logs.

Assessing the Risk of CVE-2021-28131

Access Complexity Graph

The exploitability of CVE-2021-28131 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2021-28131

This vulnerability, CVE-2021-28131, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2021-28131, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2021-28131, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2021-28131 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2021-28131 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2021-28131 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.295% (probability of exploit)

EPSS Percentile: 69.47% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 30.53% of others.

CVE-2021-28131 References

External References

CWE Common Weakness Enumeration

CWE-532

CAPEC Common Attack Pattern Enumeration and Classification

  • Fuzzing for application mapping CAPEC-215 An attacker sends random, malformed, or otherwise unexpected messages to a target application and observes the application's log or error messages returned. The attacker does not initially know how a target will respond to individual messages but by attempting a large number of message variants they may find a variant that trigger's desired behavior. In this attack, the purpose of the fuzzing is to observe the application's log and error messages, although fuzzing a target can also sometimes cause the target to enter an unstable state, causing a crash.

Vulnerable Configurations

  • cpe:2.3:a:apache:impala:2.7.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:2.7.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:2.7.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:2.7.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:2.7.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:2.7.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:2.8.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:2.8.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:2.8.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:2.8.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:2.9.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:2.9.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:2.9.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:2.9.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:2.10.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:2.10.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:2.10.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:2.10.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:2.10.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:2.10.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:2.11.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:2.11.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:2.11.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:2.11.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:2.12.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:2.12.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:2.12.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:2.12.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:3.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:3.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:3.0.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:3.0.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:3.0.1:-:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:3.0.1:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:3.0.1:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:3.0.1:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:3.1.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:3.1.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:3.1.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:3.1.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:3.2.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:3.2.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:3.2.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:3.2.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:3.3.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:3.3.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:3.3.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:3.3.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:3.4.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:3.4.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:3.4.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:3.4.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:impala:3.4.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:apache:impala:3.4.0:rc2:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2021-28131: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...
  • CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
  • CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...