CVE-2021-1071 Vulnerability Analysis & Exploit Details

CVE-2021-1071
Vulnerability Scoring

5.6
/10
Significant Risk

Security assessments indicate that CVE-2021-1071 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2021-1071 Details

Status: Modified

Last updated: 🕠 21 Nov 2024, 05:43 UTC
Originally published on: 🕙 26 Jan 2021, 22:15 UTC

Time between publication and last update: 1394 days

CVSS Release: version 3

CVSS3 Source

psirt@nvidia.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2021-1071 Vulnerability Summary

CVE-2021-1071: NVIDIA Tegra kernel in Jetson AGX Xavier Series, Jetson Xavier NX, TX1, TX2, Nano and Nano 2GB, all L4T versions prior to r32.5, contains a vulnerability in the INA3221 driver in which improper access control may lead to unauthorized users gaining access to system power usage data, which may lead to information disclosure.

Assessing the Risk of CVE-2021-1071

Access Complexity Graph

The exploitability of CVE-2021-1071 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-1071

This vulnerability, CVE-2021-1071, 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-1071, 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-1071, 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-1071 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2021-1071 poses no threat to data integrity.
  • Availability: None
    CVE-2021-1071 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

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

EPSS Score: 0.044% (probability of exploit)

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

CVE-2021-1071 References

External References

CWE Common Weakness Enumeration

NVD-CWE-Other

Vulnerable Configurations

  • cpe:2.3:o:nvidia:linux_for_tegra:-:*:*:*:*:*:*:*
    cpe:2.3:o:nvidia:linux_for_tegra:-:*:*:*:*:*:*:*
  • cpe:2.3:o:nvidia:linux_for_tegra:r21.6:*:*:*:*:*:*:*
    cpe:2.3:o:nvidia:linux_for_tegra:r21.6:*:*:*:*:*:*:*
  • cpe:2.3:o:nvidia:linux_for_tegra:r24.2.2:*:*:*:*:*:*:*
    cpe:2.3:o:nvidia:linux_for_tegra:r24.2.2:*:*:*:*:*:*:*
  • cpe:2.3:h:nvidia:jetson_agx_xavier:-:*:*:*:*:*:*:*
    cpe:2.3:h:nvidia:jetson_agx_xavier:-:*:*:*:*:*:*:*
  • cpe:2.3:h:nvidia:jetson_nano:-:*:*:*:*:*:*:*
    cpe:2.3:h:nvidia:jetson_nano:-:*:*:*:*:*:*:*
  • cpe:2.3:h:nvidia:jetson_nano_2gb:-:*:*:*:*:*:*:*
    cpe:2.3:h:nvidia:jetson_nano_2gb:-:*:*:*:*:*:*:*
  • cpe:2.3:h:nvidia:jetson_tx1:-:*:*:*:*:*:*:*
    cpe:2.3:h:nvidia:jetson_tx1:-:*:*:*:*:*:*:*
  • cpe:2.3:h:nvidia:jetson_tx2:-:*:*:*:*:*:*:*
    cpe:2.3:h:nvidia:jetson_tx2:-:*:*:*:*:*:*:*
  • cpe:2.3:h:nvidia:jetson_xavier_nx:-:*:*:*:*:*:*:*
    cpe:2.3:h:nvidia:jetson_xavier_nx:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2021-1071: 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...