Kruger&Matz com.pri.applock 13 com.pri.applock.LockUI improper export of android application components
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Kruger&Matz com.pri.applock 13. It has been classified as problematic. Affected by this issue is some unknown functionality of the component com.pri.applock.LockUI. Performing a manipulation results in improper export of android application components. This vulnerability is reported as CVE-2024-13917. The attack requires a local approach. No exploit exists.
Details
A vulnerability classified as problematic has been found in Kruger&Matz com.pri.applock 13. This affects an unknown code block of the component com.pri.applock.LockUI. The manipulation with an unknown input leads to a improper export of android application components vulnerability. CWE is classifying the issue as CWE-926. The Android application exports a component for use by other applications, but does not properly restrict which applications can launch the component or access the data it contains. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An application "com.pri.applock", which is pre-loaded on Kruger&Matz smartphones, allows a user to encrypt any application using user-provided PIN code or by using biometric data. Exposed ”com.pri.applock.LockUI“ activity allows any other malicious application, with no granted Android system permissions, to inject an arbitrary intent with system-level privileges to a protected application. One must know the protecting PIN number (it might be revealed by exploiting CVE-2024-13916) or ask the user to provide it. Vendor did not provide information about vulnerable versions. Only version (version name: 13, version code: 33) was tested and confirmed to have this vulnerability
The weakness was disclosed by Szymon Chadam. It is possible to read the advisory at cert.pl. This vulnerability is uniquely identified as CVE-2024-13917 since 03/04/2025. The exploitability is told to be easy. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Improper export of android application componentsCWE: CWE-926
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/04/2025 🔍05/30/2025 🔍
05/30/2025 🔍
06/10/2025 🔍
Sources
Advisory: cert.plResearcher: Szymon Chadam
Status: Not defined
CVE: CVE-2024-13917 (🔍)
GCVE (CVE): GCVE-0-2024-13917
GCVE (VulDB): GCVE-100-310707
Entry
Created: 05/30/2025 18:02Updated: 06/10/2025 12:26
Changes: 05/30/2025 18:02 (65), 06/10/2025 12:26 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.