CWE-925: Improper Verification of Intent by Broadcast Receiver
4 CVEs have CWE-925 as their primary weakness. 0 of them are in the CISA KEV catalog. The highest EPSS score among them is 0.406%.
The Android application uses a Broadcast Receiver that receives an Intent but does not properly verify that the Intent came from an authorized source.
Certain types of Intents, identified by action string, can only be broadcast by the operating system itself, not by third-party applications. However, when an application registers to receive these implicit system intents, it is also registered to receive any explicit intents. While a malicious application cannot send an implicit system intent, it can send an explicit intent to the target application, which may assume that any received intent is a valid implicit system intent and not an explicit intent from another application.
Child of CWE-940: Improper Verification of Source of a Communication Channel
Mitigations
- Architecture and Design: Before acting on the Intent, check the Intent Action to make sure it matches the expected System action.
Observed examples
- CVE-2025-20972: Mobile app store does not properly verify the intent by the broadcast receiver, allowing local attackers to write arbitrary files
- CVE-2024-10576: Mobile device has an application that exposes a broadcast received that allows local attackers to force a factory reset
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-925'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-925'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).