CVE-2022-42791: Race Condition
Published Sep 12, 2022
·Updated
A race condition was addressed with improved state handling. This issue is fixed in macOS Ventura 13. An app may be able to execute arbitrary code with kernel privileges.
Other sources
Accelerate Framework. A memory consumption issue was addressed with improved memory handling.
— Apple
APFS. An access issue was addressed with improved access restrictions.
— Apple
Apple Neural Engine. The issue was addressed with improved memory handling.
— Apple
AppleAVD. A memory corruption issue was addressed with improved state management.
— Apple
AppleAVD. This issue was addressed with improved checks.
— Apple
Credit
Mickey Jin@@patch1t(Trend Micro), an anonymous researcher, CVE-2022-28739, Csaba Fitzl@@theevilbit(Offensive Security), Rohit Chatterjee(University of Illinois Urbana), Justin Bui@@slyd0g(Snowflake), Linus Henze(Pinauten GmbH), Cristian Dinca(Tudor Vianu National High School of Computer Science of), Om kothawade(Zaprico Digital), Andrew Goldberg(The McCombs School of Business), The University(Texas at Austin), Felix Poulin-Belanger, CVE-2021-36690, Adam Chester(TrustedSec), Thijs Alkemade@@xnyhps(Computest Sector 7), CVE-2022-0261, CVE-2022-0318, CVE-2022-0319, CVE-2022-0351, CVE-2022-0359, CVE-2022-0361, CVE-2022-0368, CVE-2022-0392, CVE-2022-0554, CVE-2022-0572, CVE-2022-0629, CVE-2022-0685, CVE-2022-0696, CVE-2022-0714, CVE-2022-0729, CVE-2022-0943, CVE-2022-1381, CVE-2022-1420, CVE-2022-1725, CVE-2022-1616, CVE-2022-1619, CVE-2022-1620, CVE-2022-1621, CVE-2022-1629, CVE-2022-1674, CVE-2022-1733, CVE-2022-1735, CVE-2022-1769, CVE-2022-1927, CVE-2022-1942, CVE-2022-1968, CVE-2022-1851, CVE-2022-1897, CVE-2022-1898, CVE-2022-1720, CVE-2022-2000, CVE-2022-2042, CVE-2022-2124, CVE-2022-2125, CVE-2022-2126, Francisco Alonso@@revskills, P1umer@@p1umer, afang@@afang5472, xmzyshypnc@@xmzyshypnc1, Jeonghoon Shin at Theori@@singi21a(Trend Micro Zero Day Initiative), Jihwan Kim@@gPayl0ad, Dohyun Lee@@l33d0hyun, Dohyun Lee@@l33d0hyun(SSD Labs), Abdulrahman Alqabandi(Microsoft Browser Vulnerability Research), Ryan Shin(IAAI SecLab at Korea University), Dohyun Lee@@l33d0hyun(DNSLab at Korea University), Wonyoung Jung@@nonetype_pwn(KAIST Hacking Lab), Yonghwi Jin at Theori@@jinmo123(Trend Micro Zero Day Initiative), 楼梦想改造家@@18(DBAppSecurity's WeBin lab), @@jq0904(DBAppSecurity's WeBin lab), Jeff Johnson, Wang Yu(Cyberserval), Evgeny Legerov, Arsenii Kostromin (0x3c3e), Kshitij Kumar(Crowdstrike), Jai Musunuri(Crowdstrike), CVE-2022-32205, CVE-2022-32206, CVE-2022-32207, CVE-2022-32208, Sergii Kryvoblotskyi(MacPaw Inc), Tommy Muir@@Muirey03, Jiří Vinopal@@vinopaljiri(Check Point Research), Sonali Luthar(the University of Virginia), Michael Liao(the University of Illinois at Urbana), Rohan Pahwa(Rutgers University), (University of Florida), Bao Nguyen(University of Florida), Bistrit Dahal, Wojciech Reguła(SecuRing), Ron Masas (breakpoint.sh)(BreakPoint Technologies LTD), Pan ZhenPeng@@Peterpan0927, Asahi Lina@@LinaAsahi, Yutao Wang@@Jack, Yu Zhou@@yuzhou6666, Evgeny Legerov(Intevydis), Joshua Jones, Yiğit Can YILMAZ@@yilmazcanyigit, Mickey Jin@@patch1t, CVE-2022-1622, Antonio Zekic@@antoniozekic, Peter Pan ZhenPeng(STAR Labs), Tingting Yin(Tsinghua University), Zweig(Kunlun Lab), Ian Beer(Google Project Zero), Tim Michaud@@TimGMichaud(Moveworks), Xinru Chi(Pangu Lab), John Aakerblom@@jaakerblom, Wojciech Reguła@@_r3ggi(SecuRing), Ron Masas(breakpointhq), Xingwei Lin@@xwlin_roy(Ant Security Light), Yinyi Wu(Ant Security Light), CVE-2021-39537, CVE-2022-29458, Gustav Hansen(WithSecure), Ubeydullah Sümer, Ezekiel Elin, Ashwani Rajput(Nagarro Software Pvt), Srijan Shivam Mishra(The Hack Report), Jugal Goradia(Aastha Technologies), Evan Ricafort (evanricafort.com)(Invalid Web Security), Shesha Sai C (linkedin.com/in/shesha-sai-c-18585b125)(Pune), (Pune), Amod Raghunath Patwardhan(Pune), India, Yinyi Wu(Google Project Zero), ABC Research s.r.o(Google Project Zero), Natalie Silvanovich(Google Project Zero), Tommaso Bianco@@cutesmilee__, Antonio Zekic@@antoniozekic(Google Project Zero), Koh M. Nakagawa(FFRI Security Inc), Anonymous(Trend Micro Zero Day Initiative), ABC Research s.r.o., Jonathan Bar Or(Microsoft), Jonathan Zhang(Open Computing Facility), David Hoyt(Hoyt LLC), Guilherme Rambo(Best Buddy Apps), Halle Winkler@@hallewinkler(Politepix), Thijs Alkemade(Computest Sector 7), Arsenii Kostromin, Mohamed Ghannam@@_simo36, ryuzaki
Affected Software
4 affected componentsFixes available
macOS Ventura<13
13
Apple iOS and iPadOS<16
16
iPhone OS<16.0
macOS<13.0
Event History
Nov 1, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Data Sourced
via NVD·08:15 PM
DescriptionSeverityWeaknessAffected Software
Parent advisories
This vulnerability appears in the following advisories.
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2022-42795
- CVE-2022-48577
- CVE-2022-32858
- CVE-2022-32898
- CVE-2022-32899
- CVE-2022-46721
- CVE-2022-47915
- CVE-2022-47965
- CVE-2022-32889
- CVE-2022-32907
- CVE-2022-32827
- CVE-2022-32877
- CVE-2022-42789
- CVE-2022-42825
- CVE-2022-46722
- CVE-2022-32902
- CVE-2022-32904
- CVE-2022-32890
- CVE-2022-42796
- CVE-2022-42798
- CVE-2022-32940
- CVE-2022-42816
- CVE-2022-42821
- CVE-2022-42860
- CVE-2022-42819
- CVE-2022-42813
- CVE-2022-26730
- CVE-2022-32945
- CVE-2022-42838
- CVE-2022-48683
- CVE-2022-22663
- CVE-2022-32867
- CVE-2022-32205
- CVE-2022-32206
- CVE-2022-32207
- CVE-2022-32208
- CVE-2022-42814
- CVE-2022-32865
- CVE-2022-32915
- CVE-2022-32928
- CVE-2022-22643
- CVE-2022-32935
- CVE-2022-42788
- CVE-2022-48504
- CVE-2022-32905
- CVE-2022-42833
- CVE-2022-32947
- CVE-2022-42809
- CVE-2022-3437
- CVE-2022-32849
- CVE-2022-32913
- CVE-2022-32809
- CVE-2022-1622
- CVE-2022-32936
- CVE-2022-42820
- CVE-2022-42806
- CVE-2022-32864
- CVE-2022-32866
- CVE-2022-32911
- CVE-2022-32924
- CVE-2022-32914
- CVE-2022-42808
- CVE-2022-32944
- CVE-2022-42803
- CVE-2022-32926
- CVE-2022-42801
- CVE-2022-46712
- CVE-2022-42815
- CVE-2022-42834
- CVE-2022-46707
- CVE-2022-32883
- CVE-2022-32908
- CVE-2022-42810
- CVE-2021-39537
- CVE-2022-29458
- CVE-2022-42818
- CVE-2022-32879
- CVE-2022-32895
- CVE-2022-46713
- CVE-2022-42807
- CVE-2022-32918
- CVE-2022-42829
- CVE-2022-42830
- CVE-2022-42831
- CVE-2022-42832
- CVE-2022-32941
- CVE-2022-28739
- CVE-2022-32881
- CVE-2022-32862
- CVE-2022-32931
- CVE-2022-42811
- CVE-2022-42793
- CVE-2022-32876
- CVE-2022-32938
- CVE-2022-42790
- CVE-2022-32870
- CVE-2022-32934
- CVE-2022-42791
- CVE-2021-36690
- CVE-2022-48505
- CVE-2022-26699
- CVE-2022-0261
- CVE-2022-0318
- CVE-2022-0319
- CVE-2022-0351
- CVE-2022-0359
- CVE-2022-0361
- CVE-2022-0368
- CVE-2022-0392
- CVE-2022-0554
- CVE-2022-0572
- CVE-2022-0629
- CVE-2022-0685
- CVE-2022-0696
- CVE-2022-0714
- CVE-2022-0729
- CVE-2022-0943
- CVE-2022-1381
- CVE-2022-1420
- CVE-2022-1725
- CVE-2022-1616
- CVE-2022-1619
- CVE-2022-1620
- CVE-2022-1621
- CVE-2022-1629
- CVE-2022-1674
- CVE-2022-1733
- CVE-2022-1735
- CVE-2022-1769
- CVE-2022-1927
- CVE-2022-1942
- CVE-2022-1968
- CVE-2022-1851
- CVE-2022-1897
- CVE-2022-1898
- CVE-2022-1720
- CVE-2022-2000
- CVE-2022-2042
- CVE-2022-2124
- CVE-2022-2125
- CVE-2022-2126
- CVE-2022-42828
- CVE-2022-32875
- CVE-2022-42826
- CVE-2022-32886
- CVE-2022-32888
- CVE-2022-32912
- CVE-2022-42799
- CVE-2022-42823
- CVE-2022-42824
- CVE-2022-32923
- CVE-2022-32922
- CVE-2022-32892
- CVE-2022-32833
- CVE-2022-46709
- CVE-2022-37434
- CVE-2022-42800
- CVE-2022-32909
- CVE-2022-32854
- CVE-2022-32793
- CVE-2022-26744
- CVE-2022-32903
- CVE-2022-32887
- CVE-2022-32916
- CVE-2022-32917
- CVE-2022-32795
- CVE-2022-32868
- CVE-2022-32872
- CVE-2022-32871
- CVE-2022-32859
- CVE-2022-32835
- CVE-2022-32891
- CVE-2022-32925
Frequently Asked Questions
1
What is CVE-2022-42791?
CVE-2022-42791 is a vulnerability related to race condition in the software update process, which has been addressed with improved state handling.
2
Who is affected by CVE-2022-42791?
The vulnerability affects users of Apple iOS versions up to (but not including) 16 and macOS Ventura versions up to (but not including) 13.
3
What is the severity of CVE-2022-42791?
The severity of CVE-2022-42791 is not provided in the information provided.
4
How do I fix CVE-2022-42791 on Apple iOS?
To fix CVE-2022-42791 on Apple iOS, update your device to the latest version of iOS, which is 16 or later.
5
How do I fix CVE-2022-42791 on macOS Ventura?
To fix CVE-2022-42791 on macOS Ventura, update your device to the latest version of macOS Ventura, which is 13 or later.