CVE-2024-43399 Vulnerability Analysis & Exploit Details

CVE-2024-43399
Vulnerability Scoring

9.8
/10
Critical Risk

As a catastrophic security flaw, CVE-2024-43399 has severe implications, demanding immediate intervention.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2024-43399 Details

Status: Analyzed

Last updated: 🕓 20 Aug 2024, 16:21 UTC
Originally published on: 🕒 19 Aug 2024, 15:15 UTC

Time between publication and last update: 1 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2024-43399 Vulnerability Summary

CVE-2024-43399: Mobile Security Framework (MobSF) is a pen-testing, malware analysis and security assessment framework capable of performing static and dynamic analysis. Before 4.0.7, there is a flaw in the Static Libraries analysis section. Specifically, during the extraction of .a extension files, the measure intended to prevent Zip Slip attacks is improperly implemented. Since the implemented measure can be bypassed, the vulnerability allows an attacker to extract files to any desired location within the server running MobSF. This vulnerability is fixed in 4.0.7.

Assessing the Risk of CVE-2024-43399

Access Complexity Graph

The exploitability of CVE-2024-43399 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-2024-43399

With low attack complexity and no required privileges, CVE-2024-43399 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

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

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

CVE-2024-43399 References

External References

CWE Common Weakness Enumeration

CWE-23

CAPEC Common Attack Pattern Enumeration and Classification

  • Relative Path Traversal CAPEC-139 An attacker exploits a weakness in input validation on the target by supplying a specially constructed path utilizing dot and slash characters for the purpose of obtaining access to arbitrary files or resources. An attacker modifies a known path on the target in order to reach material that is not available through intended channels. These attacks normally involve adding additional path separators (/ or \) and/or dots (.), or encodings thereof, in various combinations in order to reach parent directories or entirely separate trees of the target's directory structure.
  • Manipulating Web Input to File System Calls CAPEC-76 An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.

Vulnerable Configurations

  • cpe:2.3:a:opensecurity:mobile_security_framework:-:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:-:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.8.3:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.8.3:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.8.4:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.8.4:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.8.5:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.8.5:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.8.6:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.8.6:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.8.7:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.8.7:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.8.8:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.8.8:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.8.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.8.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.8.8.2:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.8.8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9.2:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9.2:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9.3:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9.3:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9.3.4:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9.3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9.3.5:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9.3.5:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9.3.6:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9.3.6:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9.3.7:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9.3.7:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9.4:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9.4:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9.5:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9.5:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9.5.4:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9.5.4:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:0.9.5.5:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:0.9.5.5:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:1.0.3:beta:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:1.0.3:beta:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:1.1.5:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:1.1.5:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:1.1.6:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:1.1.6:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:2.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:3.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:3.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:3.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:3.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:3.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:3.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:3.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:3.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:3.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:3.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:3.2.8:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:3.2.8:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:3.2.9:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:3.2.9:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:3.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:3.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:3.3.5:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:3.3.5:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:3.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:3.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:3.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:3.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:3.4.6:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:3.4.6:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:3.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:3.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:3.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:3.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:3.6.9:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:3.6.9:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:3.7.6:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:3.7.6:*:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:3.7.8:beta:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:3.7.8:beta:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-43399: 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-2122 – A vulnerability classified as problematic was found in Thinkware Car Dashcam F800 Pro up to 20250226. Affected by this vulnerability is an unknown ...
  • 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...