CVE-2024-13915
Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-13915 is a medium-severity Improper Export of Android Application Components (CWE-926) vulnerability. Its CVSS base score is 6.9 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-16514
- 🇵🇱 CERT-PL: cert.pl
Vulnerability Data
Android based smartphones from vendors such as Ulefone and Krüger&Matz contain "com.pri.factorytest" application preloaded onto devices during manufacturing process. The application "com.pri.factorytest" (version name: 1.0, version code: 1) exposes a ”com.pri.factorytest.emmc.FactoryResetService“ service allowing any application to perform a factory reset…
more
of the device. Application update did not increment the APK version. Instead, it was bundled in OS builds released later than December 2024 (Ulefone) and April 2025 (Krüger&Matz).
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
AC-3 directly requires enforcement of authorizations on logical access, which stops an exported Android component from being reachable without proper restrictions.
Least privilege reduces the exposure of exported components by limiting unnecessary authorizations granted to other apps.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.8.26 only requires that security requirements (including access segregation) be identified and specified during development; it does not itself enforce, implement or configure the restrictions that would stop an improperly-exported Android component from being launched or accessed by unauthorized apps.
A.8.27 mandates security-by-design principles (least privilege, default-deny, distrust external input, zero-trust verification) and design reviews that can stop unsafe component export decisions, but this is only one slice of the weakness class; many export flaws arise from concrete permission/Intent-filter misconfigurations that the high-level principles and reviews do not themselves enforce.
Secure-coding standards require explicit permission declarations and intent-filter restrictions to avoid improper exports.
Security testing can detect exported components lacking proper restrictions, providing partial coverage of the weakness.
Enforcing information-access restrictions on exported Android components directly prevents unauthorized launch or data access.