Phone-number disclosure via unsanitized system logging
Published Aug 5, 2024 · Updated Oct 28, 2024
Sensitive information exposure in Who - Caller ID, Spam Block 15.0 for Android allows local users to read outgoing phone numbers. When a call session begins, the application writes the outgoing phone number to the shared Android system log without sanitizing it. Access requires a co-located process able to read system logs, and the reported impact is limited to disclosure of logged phone numbers.
Summary
What happened
Sensitive information exposure in Who - Caller ID, Spam Block 15.0 for Android allows local users to read outgoing phone numbers. When a call session begins, the application writes the outgoing phone number to the shared Android system log without sanitizing it. Access requires a co-located process able to read system logs, and the reported impact is limited to disclosure of logged phone numbers.
The record
- CVE
- CVE-2024-40096
- Published
- Aug 5, 2024
- Updated
- Oct 28, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-532, T1533
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 5, 2024CVE publishedPublication date reported by the CVE source.
- Oct 28, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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