Authentication policy violation via unauthorized code execution
Published Apr 2, 2021 · Updated Aug 4, 2024
Code execution in the Security component of affected Apple iOS, iPadOS, and watchOS releases allows attackers to violate authentication policy. Apple identifies the locus only as the Security component and states that improved checks addressed the issue; the unchecked operation and input remain undisclosed. NVD assesses local access without privileges and required user interaction, while successful exploitation permits unauthorized code execution with a resulting authentication-policy violation.
Summary
What happened
Code execution in the Security component of affected Apple iOS, iPadOS, and watchOS releases allows attackers to violate authentication policy. Apple identifies the locus only as the Security component and states that improved checks addressed the issue; the unchecked operation and input remain undisclosed. NVD assesses local access without privileges and required user interaction, while successful exploitation permits unauthorized code execution with a resulting authentication-policy violation.
The record
- CVE
- CVE-2020-27951
- Published
- Apr 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- iOS
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- unauthenticated
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 <12.5
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
No sourced classifications are available.
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