CVE-2023-41325 Vulnerability Analysis & Exploit Details

CVE-2023-41325
Vulnerability Scoring

7.4
/10
Very High Risk

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

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: High
    High-level privileges are required for exploitation.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2023-41325 Details

Status: Modified

Last updated: 🕗 21 Nov 2024, 08:21 UTC
Originally published on: 🕗 15 Sep 2023, 20:15 UTC

Time between publication and last update: 432 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2023-41325 Vulnerability Summary

CVE-2023-41325: OP-TEE is a Trusted Execution Environment (TEE) designed as companion to a non-secure Linux kernel running on Arm; Cortex-A cores using the TrustZone technology. Starting in version 3.20 and prior to version 3.22, `shdr_verify_signature` can make a double free. `shdr_verify_signature` used to verify a TA binary before it is loaded. To verify a signature of it, allocate a memory for RSA key. RSA key allocate function (`sw_crypto_acipher_alloc_rsa_public_key`) will try to allocate a memory (which is optee’s heap memory). RSA key is consist of exponent and modulus (represent as variable `e`, `n`) and it allocation is not atomic way, so it may succeed in `e` but fail in `n`. In this case sw_crypto_acipher_alloc_rsa_public_key` will free on `e` and return as it is failed but variable ‘e’ is remained as already freed memory address . `shdr_verify_signature` will free again that memory (which is `e`) even it is freed when it failed allocate RSA key. A patch is available in version 3.22. No known workarounds are available.

Assessing the Risk of CVE-2023-41325

Access Complexity Graph

The exploitability of CVE-2023-41325 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-2023-41325

The exploitability of CVE-2023-41325 is influenced by multiple factors. Security teams should analyze system configurations and apply appropriate countermeasures to mitigate threats.

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-2023-41325, 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-2023-41325, 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-2023-41325 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2023-41325 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2023-41325 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.042% (probability of exploit)

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

CVE-2023-41325 References

External References

CWE Common Weakness Enumeration

CWE-415

Vulnerable Configurations

  • cpe:2.3:o:linaro:op-tee:3.20.0:-:*:*:*:*:*:*
    cpe:2.3:o:linaro:op-tee:3.20.0:-:*:*:*:*:*:*
  • cpe:2.3:o:linaro:op-tee:3.20.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:linaro:op-tee:3.20.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linaro:op-tee:3.21.0:-:*:*:*:*:*:*
    cpe:2.3:o:linaro:op-tee:3.21.0:-:*:*:*:*:*:*
  • cpe:2.3:o:linaro:op-tee:3.21.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:linaro:op-tee:3.21.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linaro:op-tee:3.22.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:linaro:op-tee:3.22.0:rc1:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2023-41325: 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-27636 – Bypass/Injection vulnerability in Apache Camel. This issue affects Apache Camel: from 4.10.0 through <= 4.10.1, from 4.8.0 through <= 4.8.4, from ...
  • CVE-2025-2121 – A vulnerability classified as critical has been found in Thinkware Car Dashcam F800 Pro up to 20250226. Affected is an unknown function of the comp...
  • CVE-2025-2120 – A vulnerability was found in Thinkware Car Dashcam F800 Pro up to 20250226. It has been rated as problematic. This issue affects some unknown proce...
  • CVE-2025-2119 – A vulnerability was found in Thinkware Car Dashcam F800 Pro up to 20250226. It has been declared as problematic. This vulnerability affects unknown...
  • CVE-2025-2118 – A vulnerability was found in Quantico Tecnologia PRMV 6.48. It has been classified as critical. This affects an unknown part of the file /admin/log...