Persistent lock failure via Status Bar UI handling
Published Oct 25, 2023 · Updated Feb 13, 2025
Improper security checks in Apple iOS and iPadOS before 17.1 allow attackers to prevent device locking via unspecified vectors. Apple identifies the Status Bar and improved UI handling but has not published the faulty UI operation or attacker-controlled input. The access prerequisite is undisclosed; successful exploitation leaves the device persistently unlocked rather than causing a crash or reboot.
Summary
What happened
Improper security checks in Apple iOS and iPadOS before 17.1 allow attackers to prevent device locking via unspecified vectors. Apple identifies the Status Bar and improved UI handling but has not published the faulty UI operation or attacker-controlled input. The access prerequisite is undisclosed; successful exploitation leaves the device persistently unlocked rather than causing a crash or reboot.
The record
- CVE
- CVE-2023-40445
- Published
- Oct 25, 2023
- Updated
- Feb 13, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-358, T1629
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 25, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=unspecified <17.1
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