CVE-2025-24804 Vulnerability Analysis & Exploit Details

CVE-2025-24804
Vulnerability Scoring

4.3
/10
Medium Risk

The vulnerability CVE-2025-24804 could compromise system integrity but typically requires user interaction to be exploited.

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: Required
    User interaction is necessary for successful exploitation.

CVE-2025-24804 Details

Status: Analyzed

Last updated: 🕔 23 May 2025, 17:18 UTC
Originally published on: 🕖 05 Feb 2025, 19:15 UTC

Time between publication and last update: 106 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:R/S:U/C:N/I:N/A:L

CVE-2025-24804 Vulnerability Summary

CVE-2025-24804: Mobile Security Framework (MobSF) is an automated, all-in-one mobile application (Android/iOS/Windows) pen-testing, malware analysis and security assessment framework. According to Apple's documentation for bundle ID's, it must contain only alphanumeric characters (A–Z, a–z, and 0–9), hyphens (-), and periods (.). However, an attacker can manually modify this value in the `Info.plist` file and add special characters to the `<key>CFBundleIdentifier</key>` value. When the application parses the wrong characters in the bundle ID, it encounters an error. As a result, it will not display content and will throw a 500 error instead. The only way to make the pages work again is to manually remove the malicious application from the system. This issue has been addressed in version 4.3.1 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

Assessing the Risk of CVE-2025-24804

Access Complexity Graph

The exploitability of CVE-2025-24804 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-2025-24804

With low attack complexity and no required privileges, CVE-2025-24804 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-2025-24804, 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-2025-24804, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2025-24804 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2025-24804 poses no threat to data integrity.
  • Availability: Low
    CVE-2025-24804 may slightly degrade system performance without fully affecting service 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.045% (probability of exploit)

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

CVE-2025-24804 References

External References

CWE Common Weakness Enumeration

NVD-CWE-Other

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:*:*:*:*:*:*
  • cpe:2.3:a:opensecurity:mobile_security_framework:4.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:opensecurity:mobile_security_framework:4.0.5:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-24804: 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-5584 – A vulnerability was found in PHPGurukul Hospital Management System 4.0. It has been classified as problematic. Affected is an unknown function of t...
  • CVE-2025-5583 – A vulnerability classified as critical has been found in CodeAstro Real Estate Management System 1.0. Affected is an unknown function of the file /...
  • CVE-2018-25112 – An unauthenticated remote attacker may use an uncontrolled resource consumption in the IEC 61131 program of the affected products by creating large...
  • CVE-2025-5582 – A vulnerability was found in CodeAstro Real Estate Management System 1.0. It has been rated as critical. This issue affects some unknown processing...
  • CVE-2025-5581 – A vulnerability was found in CodeAstro Real Estate Management System 1.0. It has been declared as critical. This vulnerability affects unknown code...