Application-state alteration via faulty setting propagation
Published Apr 2, 2021 · Updated Aug 4, 2024
HomeKit setting-propagation failure in affected Apple operating systems allows attackers to alter application state. Affected releases include iOS, iPadOS, and tvOS before 14.0, watchOS before 7.0, and affected macOS releases before 11.1. Apple identifies HomeKit as the locus but has not published the faulty message path or operation; exploitation requires a privileged network position.
Summary
What happened
HomeKit setting-propagation failure in affected Apple operating systems allows attackers to alter application state. Affected releases include iOS, iPadOS, and tvOS before 14.0, watchOS before 7.0, and affected macOS releases before 11.1. Apple identifies HomeKit as the locus but has not published the faulty message path or operation; exploitation requires a privileged network position.
The record
- CVE
- CVE-2020-9978
- Published
- Apr 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- T1565.002
- Attack vector
- adjacent
- Privileges
- admin
Timeline
How it unfolded
- Apr 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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 <14.0
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