# CVE-2024-13915: Unrestricted Access to Exported Service in com.pri.factorytest

> A preinstalled Android factory test application exposes a service allowing any app to trigger a factory reset, causing data loss and denial of service.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2025
- **Updated:** 10 Jun 2025
- **Also known as:** GHSA-9m9c-m3m8-59vc

## What is CVE-2024-13915?

CVE-2024-13915 is a medium-severity missing authorization vulnerability in Krüger&Matz com.pri.factorytest, published on 30 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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 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).

Weakness: CWE-926 (Improper Export of Android Application Components)

## Which versions are affected by CVE-2024-13915?


## How do I fix CVE-2024-13915?

No fix has been published for CVE-2024-13915 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-13915 being exploited?

There is no known exploitation of CVE-2024-13915 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-13915 and fix it if it is affected.

What it is: CVE-2024-13915 is a medium-severity missing authorization vulnerability in Krüger&Matz com.pri.factorytest, published on 30 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13915 in the wild and no public exploit code.

Affected product: Krüger&Matz com.pri.factorytest. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-13915/ (Markdown: https://insights.sbomify.com/CVE-2024-13915/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-13915
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-13915
- OSV: https://osv.dev/vulnerability/CVE-2024-13915

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-13915/
Summaries are generated and may contain mistakes; the official description above is the record.