CVE-2023-42936: Race Condition

Published Dec 11, 2023
·
Updated

Accessibility. A privacy issue was addressed with improved private data redaction for log entries.

Other sources

Accessibility. This issue was addressed with improved state management.

— Apple

Accounts. A privacy issue was addressed with improved private data redaction for log entries.

— Apple

AppleEvents. This issue was addressed with improved redaction of sensitive information.

— Apple

AppleGraphicsControl. Multiple memory corruption issues were addressed with improved input validation.

— Apple

AppleVA. The issue was addressed with improved memory handling.

— Apple

Credit

Csaba Fitzl@@theevilbit(OffSec), Mickey Jin@@patch1t, an anonymous researcher, Marc Newlin(SkySafe), Koh M. Nakagawa@@tsunek0h, CVE-2023-38545, CVE-2023-38039, CVE-2023-38546, Yann GASCUEL(Alter Solutions), Anthony Cruz Tyrant Corp@@App, Wojciech Regula(SecuRing), Zhenjiang Zhao(Pangu Team), Qianxin, Junsung Lee, Meysam Firouzi@@R00tkitSMM, Michael DePlante@@izobashi(Trend Micro Zero Day Initiative), Pan ZhenPeng@@Peterpan0927(STAR Labs SG Pte), Eloi Benoist-Vanderbeken@@elvanderb(Synacktiv), CVE-2023-42893, CVE-2023-3618, CVE-2020-19185, CVE-2020-19186, CVE-2020-19187, CVE-2020-19188, CVE-2020-19189, CVE-2020-19190, Ron Masas(BreakPoint), Csaba Fitzl@@theevilbit(Offensive Security), Arsenii Kostromin (0x3c3e), Mattie Behrens, Joshua Jewett@@JoshJewett33, Zhongquan Li@@Guluisacat, Zhongquan Li@@Guluisacat(Dawn Security Lab of JingDong), CVE-2023-5344, Pwn2car, Zoom Offensive Security Team, Nan Wang@@eternalsakura13(360 Vulnerability Research Institute), rushikesh nandedkar, SungKwon Lee (Demon.Team), Noah Roskin-Frazee, Pr, Ivan Fratric(Google Project Zero), (Trend Micro Zero Day Initiative), Don Clarke, Kirin@@Pwnrin, Clément Lecigne(Google's Threat Analysis Group), rushikesh nandedka, Christopher Reynolds, Aymane Chabat, ARJUN S D, Andrew Goldberg(The McCombs School of Business), The University(Texas at Austin), Yiğit Can YILMAZ@@yilmazcanyigit(Offensive Security), (Offensive Security), Yiğit Can YILMAZ@@yilmazcanyigit, Jewel Lambert, Zhipeng Huo@@R3dF09(Tencent Security Xuanwu Lab), Apple

Affected Software

14 affected componentsFixes available
Apple macOS Sonoma<14.2
14.2
Apple tvOS<17.2
17.2
Apple WatchOS<10.2
10.2
Apple macOS Monterey<12.7.2
12.7.2
Apple macOS Ventura<13.6.3
13.6.3
Apple iOS<17.2
17.2
Apple iPadOS<17.2
17.2
Apple iPadOS<17.2
Apple iPhone OS<17.2
Apple macOS>=12.0<12.7.2
Apple macOS>=13.0<13.6.3
Apple macOS>=14.0<14.2
Apple tvOS<17.2
Apple WatchOS<10.2

Event History

Dec 11, 2023
Data Sourced
via Apple·12:00 AM
DescriptionWeaknessAffected Software
Updated
via Apple·12:00 AM
DescriptionWeakness
Updated
via Apple·12:00 AM
Description
Updated
via Apple·12:00 AM
DescriptionWeaknessAffected Software
Updated
via Apple·12:00 AM
Affected Software
Updated
via Apple·12:00 AM
DescriptionAffected Software
Mar 28, 2024
CVE Published
via MITRE·03:39 PM
Data Sourced
via MITRE·03:39 PM
DescriptionWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2023-42936?

CVE-2023-42936 has been classified as a medium severity vulnerability due to its potential impact on sensitive information.

2

How do I fix CVE-2023-42936?

To fix CVE-2023-42936, update your device to the latest versions: macOS Monterey 12.7.2, macOS Ventura 13.6.3, iOS 17.2, iPadOS 17.2, tvOS 17.2, watchOS 10.2, or macOS Sonoma 14.2.

3

Which devices are affected by CVE-2023-42936?

CVE-2023-42936 affects various Apple devices running certain versions of macOS, iOS, iPadOS, tvOS, and watchOS.

4

What kind of issue is CVE-2023-42936?

CVE-2023-42936 is a sandbox vulnerability that allows for insufficient redaction of sensitive information.

5

Can I still use my device if it is exposed to CVE-2023-42936?

Although you can continue using your device, it is highly recommended to update immediately to mitigate the risks associated with CVE-2023-42936.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203