System-privileged intent execution via exported activity
Published May 30, 2025 · Updated Jun 10, 2025
Intent injection in Kruger&Matz AppLock 13 allows local users to invoke protected apps with system privileges through a malicious app. The exported com.pri.applock.LockUI activity accepts an arbitrary intent from an app with no Android permissions and launches it with AppLock's system-level privileges. Exploitation requires the protecting PIN or active user entry of that PIN; successful use grants the injected intent the privileges available to the targeted protected app.
Summary
What happened
Intent injection in Kruger&Matz AppLock 13 allows local users to invoke protected apps with system privileges through a malicious app. The exported com.pri.applock.LockUI activity accepts an arbitrary intent from an app with no Android permissions and launches it with AppLock's system-level privileges. Exploitation requires the protecting PIN or active user entry of that PIN; successful use grants the injected intent the privileges available to the targeted protected app.
The record
- CVE
- CVE-2024-13917
- Published
- May 30, 2025
- Updated
- Jun 10, 2025
- Vendor
- Kruger&Matz
- Product
- Kruger&Matz AppLock
- Classifications
- CWE-926, T1626
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 30, 2025CVE publishedPublication date reported by the CVE source.
- Jun 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=13
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo