False microphone-use indication via recording-state race
Published Jul 12, 2023 · Updated Nov 6, 2024
A race condition in Android 12, 12L, and 13 allows attackers to leave the microphone privacy indicator showing an incorrect recording state. In AudioPolicyService::startInput, a silenced client is registered by startRecording and registered again when unsilenced, so reference counting leaves stale AppOps attribution. User interaction is required, and the bounded consequence is a misleading microphone-use indication rather than audio capture or code execution.
Summary
What happened
A race condition in Android 12, 12L, and 13 allows attackers to leave the microphone privacy indicator showing an incorrect recording state. In AudioPolicyService::startInput, a silenced client is registered by startRecording and registered again when unsilenced, so reference counting leaves stale AppOps attribution. User interaction is required, and the bounded consequence is a misleading microphone-use indication rather than audio capture or code execution.
The record
- CVE
- CVE-2023-21262
- Published
- Jul 12, 2023
- Updated
- Nov 6, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-362
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 12, 2023CVE publishedPublication date reported by the CVE source.
- Nov 6, 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=12
- Affected versionversion=12L
- Affected versionversion=13
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