Local task hijacking via default task affinity
Published Jul 20, 2025 · Updated Jul 21, 2025
Task hijacking in CallApp: Caller ID & Block 2.0.0 through 2.0.4 allows local users to display a phishing activity in place of the app. AndroidManifest.xml leaves taskAffinity at its package-name default, so a malicious app can claim caller.id.phone.number.block and occupy the task root. Exploitation requires a malicious app to be installed and run before CallApp is launched; the spoofed activity can capture entered data or induce permission grants.
Summary
What happened
Task hijacking in CallApp: Caller ID & Block 2.0.0 through 2.0.4 allows local users to display a phishing activity in place of the app. AndroidManifest.xml leaves taskAffinity at its package-name default, so a malicious app can claim caller.id.phone.number.block and occupy the task root. Exploitation requires a malicious app to be installed and run before CallApp is launched; the spoofed activity can capture entered data or induce permission grants.
The record
- CVE
- CVE-2025-7889
- Published
- Jul 20, 2025
- Updated
- Jul 21, 2025
- Vendor
- CallApp Software Ltd.
- Product
- CallApp: Caller ID & Block
- Classifications
- CWE-926, T1655
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 20, 2025CVE publishedPublication date reported by the CVE source.
- Jul 21, 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=2.0.0
- Affected versionversion=2.0.1
- Affected versionversion=2.0.2
- Affected versionversion=2.0.3
- Affected versionversion=2.0.4
What conditions does exploitation require?
What is affected?
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
- caller.id.phone.number.block task-hijacking proof of conceptproof of concept · demonstrated
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