CVE-2022-32899: High severity apple ios, ipados, and watchos vulnerability
Published Sep 12, 2022
·Updated
Accelerate Framework. A memory consumption issue was addressed with improved memory handling.
Other sources
APFS. An access issue was addressed with improved access restrictions.
— Apple
Apple Neural Engine. The issue was addressed with improved memory handling.
— Apple
The issue was addressed with improved memory handling. This issue is fixed in iOS 15.7 and iPadOS 15.7, iOS 16, macOS Ventura 13, watchOS 9. An app may be able to execute arbitrary code with kernel privileges.
— MITRE
Credit
Mohamed Ghannam@@_simo36, Yinyi Wu(Google Project Zero), ABC Research s.r.o(Google Project Zero), Natalie Silvanovich(Google Project Zero), Tommaso Bianco@@cutesmilee__, Antonio Zekic@@antoniozekic, John Aakerblom@@jaakerblom, Antonio Zekic@@antoniozekic(Google Project Zero), an anonymous researcher, Wojciech Reguła@@_r3ggi(SecuRing), Koh M. Nakagawa(FFRI Security Inc), Mickey Jin@@patch1t, Anonymous(Trend Micro Zero Day Initiative), ABC Research s.r.o., Jonathan Bar Or(Microsoft), Mickey Jin@@patch1t(Trend Micro), 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, 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), Linus Henze(Pinauten GmbH), 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, Csaba Fitzl@@theevilbit(Offensive Security), 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, CVE-2022-1622, 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), 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, CVE-2022-28739, Rohit Chatterjee(University of Illinois Urbana), Justin Bui@@slyd0g(Snowflake), 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, ryuzaki
Affected Software
9 affected componentsFixes available
Apple WatchOS<9
9
Apple macOS Ventura<13
13
Apple iOS<16
16
Apple iOS<15.7
15.7
Apple iPadOS<15.7
15.7
Apple iPadOS<15.7
Apple iPhone OS<15.7
Apple macOS<13.0
Apple WatchOS<9.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
DescriptionSeverityAffected Software
Parent advisories
This vulnerability appears in the following advisories.
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2022-42795
- CVE-2022-32907
- CVE-2022-32858
- CVE-2022-32898
- CVE-2022-32899
- CVE-2022-32889
- CVE-2022-32854
- CVE-2022-32928
- CVE-2022-32903
- CVE-2022-1622
- CVE-2022-32913
- CVE-2022-32864
- CVE-2022-32866
- CVE-2022-32911
- CVE-2022-32914
- CVE-2022-32894
- CVE-2022-32883
- CVE-2022-32908
- CVE-2022-32879
- CVE-2022-32881
- CVE-2022-32870
- CVE-2021-36690
- CVE-2022-32835
- CVE-2022-32875
- CVE-2022-32886
- CVE-2022-32888
- CVE-2022-32912
- CVE-2022-32891
- CVE-2022-32893
- CVE-2022-46709
- CVE-2022-32925
- CVE-2022-48577
- CVE-2022-46721
- CVE-2022-47915
- CVE-2022-47965
- 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-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-32809
- CVE-2022-32936
- CVE-2022-42820
- CVE-2022-42806
- CVE-2022-32924
- 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-42810
- CVE-2021-39537
- CVE-2022-29458
- CVE-2022-42818
- 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-32862
- CVE-2022-32931
- CVE-2022-42811
- CVE-2022-42793
- CVE-2022-32876
- CVE-2022-32938
- CVE-2022-42790
- CVE-2022-32934
- CVE-2022-42791
- 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-42826
- CVE-2022-42799
- CVE-2022-42823
- CVE-2022-42824
- CVE-2022-32923
- CVE-2022-32922
- CVE-2022-32892
- CVE-2022-32833
- CVE-2022-37434
- CVE-2022-42800
- CVE-2022-32909
- CVE-2022-32793
- CVE-2022-26744
- 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-32929
Frequently Asked Questions
1
What is the vulnerability ID for this issue?
The vulnerability ID for this issue is CVE-2022-32899.
2
What is the affected software?
The affected software includes macOS Ventura (up to version 13), iOS (up to version 16), iPadOS (up to version 15.7), and watchOS (up to version 9).
3
How was the issue addressed?
The issue was addressed with improved memory handling.
4
Is there a remedy available?
Yes, Apple has provided remedies for the affected software versions.
5
Where can I find more information?
More information can be found on the following Apple support pages: [Support Page 1](https://support.apple.com/en-us/HT213446), [Support Page 2](https://support.apple.com/en-us/HT213445), [Support Page 3](https://support.apple.com/en-us/HT213486).