Dictionary disclosure and modification via late authorization
Published Jan 17, 2025 · Updated Mar 13, 2025
Authorization bypass in Android 6.0 through 8.1 allows local users to read, update, or delete personal-dictionary entries. UserDictionaryProvider's update() and delete() methods modify exported-provider database rows before canCallerAccessUserDictionary() rejects unauthorized callers. Any locally installed app can invoke the provider without permission or user interaction; timed conditional updates can indirectly disclose entries, while direct calls can alter or erase them.
Summary
What happened
Authorization bypass in Android 6.0 through 8.1 allows local users to read, update, or delete personal-dictionary entries. UserDictionaryProvider's update() and delete() methods modify exported-provider database rows before canCallerAccessUserDictionary() rejects unauthorized callers. Any locally installed app can invoke the provider without permission or user interaction; timed conditional updates can indirectly disclose entries, while direct calls can alter or erase them.
The record
- CVE
- CVE-2018-9375
- Published
- Jan 17, 2025
- Updated
- Mar 13, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-269, T1404
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 17, 2025CVE publishedPublication date reported by the CVE source.
- Mar 13, 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=Android Kernel
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- IOActive UserDictionaryProvider 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