Summary
Partial Denial of Service (DoS)
Product: MobSF
Version: v4.2.9
CWE-ID: CWE-1287: Improper Validation of Specified Type of Input
CVSS vector v.4.0: 6.9 (AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N)
CVSS vector v.3.1: 6.5 (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H)
Description: DoS in the Scans Results and iOS Dynamic Analyzer functionality
Impact: Leveraging this vulnerability would make Scans Results and iOS Dynamic Analyzer pages unavailable.
Vulnerable component: urls.py
https://github.com/MobSF/Mobile-Security-Framework-MobSF/blob/d1d3b7a9aeb1a8c8c7c229a3455b19ade9fa8fe0/mobsf/MobSF/urls.py#L401
Exploitation conditions: A malicious application was uploaded to the MobSF.
Mitigation: Check the uploaded bundle IDs against the regex.
Researcher: Oleg Surnin (Positive Technologies)
Research
Researcher discovered zero-day vulnerability Partial Denial of Service (DoS) in MobSF in the Scans Results and iOS Dynamic Analyzer functionality.
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 (.).
(https://developer.apple.com/documentation/bundleresources/information-property-list/cfbundleidentifier)
However, an attacker can manually modify this value in Info.plist file and add special characters to the <key>CFBundleIdentifier</key> value.
In the urls.py file URL rules are defined.
https://github.com/MobSF/Mobile-Security-Framework-MobSF/blob/d1d3b7a9aeb1a8c8c7c229a3455b19ade9fa8fe0/mobsf/MobSF/urls.py#L401
Listing 3.
bundle_id_regex = r'(?P<bundle_id>([a-zA-Z0-9]{1}[\w.-]{1,255}))$'
# skip code
re_path(fr'^ios/view_report/{bundle_id_regex}',
ios_view_report.ç,
name='ios_view_report'),
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.
Vulnerability reproduction
To reproduce the vulnerability, follow the steps described below.
• Unzip the IPA file of any iOS application.
Listing 4. Unzipping the file
unzip test.ipa
• Modify the value of <key>CFBundleIdentifier</key> by adding restricted characters in the Info.plist file.
*Figure 7. Example with ' character`
• Zip the modified IPA file.
Listing 5. Zipping the file
zip -r dos.ipa Payload/
• Upload the modified IPA file to Static Analysis and wait until it finished
• Open the following pages:http://mobsf/recent_scans/http://mobsf/ios/dynamic_analysis/
Figure 8. DoS Example
Figure 9. DoS Example
Please, assign all credits to Oleg Surnin (Positive Technologies)
Impact
CVE-2025-24804 has a CVSS score of 6.5 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.3.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-24804? CVE-2025-24804 is a high-severity security vulnerability in mobsf (pip), affecting versions <= 4.3.0. It is fixed in 4.3.1.
- How severe is CVE-2025-24804? CVE-2025-24804 has a CVSS score of 6.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of mobsf are affected by CVE-2025-24804? mobsf (pip) versions <= 4.3.0 is affected.
- Is there a fix for CVE-2025-24804? Yes. CVE-2025-24804 is fixed in 4.3.1. Upgrade to this version or later.
- Is CVE-2025-24804 exploitable, and should I be worried? Whether CVE-2025-24804 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-24804 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-24804? Upgrade
mobsfto 4.3.1 or later.