CVE-2023-42923: Race Condition
Accessibility. A privacy issue was addressed with improved private data redaction for log entries.
Other sources
Accounts. A privacy issue was addressed with improved private data redaction for log entries.
— Apple
Assets. An issue was addressed with improved handling of temporary files.
— Apple
AVEVideoEncoder. This issue was addressed with improved redaction of sensitive information.
— Apple
Bluetooth. The issue was addressed with improved checks.
— Apple
CallKit. This issue was addressed with improved checks
— Apple
Credit
Affected Software
Event History
Parent advisories
This vulnerability appears in the following advisories.
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2023-42937
- CVE-2023-42919
- CVE-2023-42896
- CVE-2023-42884
- CVE-2023-45866
- CVE-2023-42941
- CVE-2023-42962
- CVE-2023-42922
- CVE-2023-42898
- CVE-2023-42899
- CVE-2023-42888
- CVE-2023-42974
- CVE-2023-42914
- CVE-2023-42893
- CVE-2023-42923
- CVE-2023-42936
- CVE-2023-42897
- CVE-2023-42947
- CVE-2023-40389
- CVE-2023-42890
- CVE-2023-42883
- CVE-2023-42950
- CVE-2023-42956
- CVE-2023-43010
Frequently Asked Questions
What is the severity of CVE-2023-42923?
The severity of CVE-2023-42923 is high due to the potential for unauthorized access to private browsing tabs.
How do I fix CVE-2023-42923?
You can fix CVE-2023-42923 by updating to iOS 17.2 or iPadOS 17.2.
What are the affected versions in CVE-2023-42923?
CVE-2023-42923 affects versions of iOS and iPadOS prior to 17.2.
What impact does CVE-2023-42923 have on users?
CVE-2023-42923 allows unauthorized access to Private Browsing tabs without user authentication.
Which devices are vulnerable to CVE-2023-42923?
Devices running iOS and iPadOS versions before 17.2 are vulnerable to CVE-2023-42923.