Autofill data disclosure via forged package identity
Published Nov 14, 2024 · Updated Nov 20, 2024
Information disclosure in Android 8.0 and 8.1 Autofill allows local users to obtain autofill data by forging an app package name. The Autofill server accepts the activity component embedded in an app-supplied AssistStructure without comparing it to the calling activity, allowing a forged identity to reach the selected Autofill service. A locally installed malicious app needs no additional execution privileges or user interaction, and the consequence is limited to data exposed through Autofill.
Summary
What happened
Information disclosure in Android 8.0 and 8.1 Autofill allows local users to obtain autofill data by forging an app package name. The Autofill server accepts the activity component embedded in an app-supplied AssistStructure without comparing it to the calling activity, allowing a forged identity to reach the selected Autofill service. A locally installed malicious app needs no additional execution privileges or user interaction, and the consequence is limited to data exposed through Autofill.
The record
- CVE
- CVE-2017-13227
- Published
- Nov 14, 2024
- Updated
- Nov 20, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 14, 2024CVE publishedPublication date reported by the CVE source.
- Nov 20, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=8.0
- Affected versionversion=8.1
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
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