Privacy preference bypass via inherited TCC permissions
Published Aug 24, 2021 · Updated Aug 3, 2024
TCC permissions bypass in Apple iOS, iPadOS, macOS, and watchOS allows malicious applications to bypass Privacy preferences. The TCC subsystem improperly inherits permissions where additional restrictions should apply; Apple has not disclosed the affected code path. Exploitation requires a malicious application to run locally on releases before iOS and iPadOS 15.2, macOS 12.1, or watchOS 8.3, with no published integrity or availability impact.
Summary
What happened
TCC permissions bypass in Apple iOS, iPadOS, macOS, and watchOS allows malicious applications to bypass Privacy preferences. The TCC subsystem improperly inherits permissions where additional restrictions should apply; Apple has not disclosed the affected code path. Exploitation requires a malicious application to run locally on releases before iOS and iPadOS 15.2, macOS 12.1, or watchOS 8.3, with no published integrity or availability impact.
The record
- CVE
- CVE-2021-30964
- Published
- Aug 24, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-732
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=unspecified <15.2
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