Account-name disclosure via production notification logging
Published Jan 24, 2023 · Updated Apr 2, 2025
Sensitive information exposure in Google Android Automotive OS 12L allows local users to read account names from System UI logs. CarNotificationListener.java passes StatusBarNotification.getKey() directly to logging in production user builds, although the key can contain PII. Low-privileged local access with no user interaction is sufficient to obtain logged account identifiers; integrity and availability are unaffected.
Summary
What happened
Sensitive information exposure in Google Android Automotive OS 12L allows local users to read account names from System UI logs. CarNotificationListener.java passes StatusBarNotification.getKey() directly to logging in production user builds, although the key can contain PII. Low-privileged local access with no user interaction is sufficient to obtain logged account identifiers; integrity and availability are unaffected.
The record
- CVE
- CVE-2022-20458
- Published
- Jan 24, 2023
- Updated
- Apr 2, 2025
- Vendor
- Product
- Android Automotive OS
- Classifications
- CWE-532, T1533
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 24, 2023CVE publishedPublication date reported by the CVE source.
- Apr 2, 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-12L
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
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