{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-13917 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-13917 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-13917 is a high-severity missing authorization vulnerability in Kruger\u0026Matz com.pri.applock, published on 30 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-13917 and fix it if it is affected.\n\nWhat it is: CVE-2024-13917 is a high-severity missing authorization vulnerability in Kruger\u0026Matz com.pri.applock, published on 30 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-13917 in the wild and no public exploit code.\n\nAffected product: Kruger\u0026Matz com.pri.applock. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-13917/ (Markdown: https://insights.sbomify.com/CVE-2024-13917/index.md)","id":"CVE-2024-13917","markdown":"https://insights.sbomify.com/CVE-2024-13917/index.md","name":"CVE-2024-13917","record":{"aliases":["GHSA-89vx-m8mc-p558"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Android app lock","requires_auth":"none","summary":"A malicious app can inject intents into the AppLock activity to bypass security controls, requiring an update to the pre-loaded application.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-926","name":"Improper Export of Android Application Components"}],"description":"An application \"com.pri.applock\", which is pre-loaded on Kruger\u0026Matz smartphones, allows a user to encrypt any application using user-provided PIN code or by using biometric data.\nExposed ”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.\n\nOnly version (version name: 13, version code: 33) was tested and confirmed to have this vulnerability. \nApplication update was released in April 2025.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Intent Injection in Kruger\u0026Matz AppLock application","id":"CVE-2024-13917","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Laravel Reflected XSS via Request Parameter in Debug-Mode Error Page","id":"CVE-2024-13918"},"packages":[],"prev":{"headline":"Exposure of Applications' Encryption PINs in Kruger\u0026Matz AppLock","id":"CVE-2024-13916"},"products":["com.pri.applock"],"published":"2025-05-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-06-10","vendors":["Kruger\u0026Matz"]},"summary":"A malicious app can inject intents into the AppLock activity to bypass security controls, requiring an update to the pre-loaded application.","url":"https://insights.sbomify.com/CVE-2024-13917/"}