CVE-2022-42798: Buffer Overflow

Published Oct 24, 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

Apple TV. The issue was addressed with improved handling of caches.

— Apple

AppleAVD. A memory corruption issue was addressed with improved state management.

— Apple

AppleAVD. This issue was addressed with improved checks.

— Apple

Credit

Anonymous(Trend Micro Zero Day Initiative), 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, 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, Mohamed Ghannam@@_simo36, ryuzaki, Willy R. Vasquez(The University of Texas at Austin), IES Red Team(ByteDance), Mir Masood Ali(Illinois at Chicago), PhD student(Illinois at Chicago), University(Illinois at Chicago), MS student(Illinois at Chicago), Stony Brook University; Mohammad Ghasemisharif(Illinois at Chicago), PhD Candidate(Illinois at Chicago), Associate Professor(Illinois at Chicago), Stony Brook University; Jason Polakis(Illinois at Chicago), Dr Hideaki Goto(Tohoku University), Japan

Affected Software

15 affected componentsFixes available
Apple macOS Big Sur<11.7.1
11.7.1
Apple tvOS<16.1
16.1
Apple WatchOS<9.1
9.1
Apple macOS Monterey<12.6.1
12.6.1
Apple macOS Ventura<13
13
Apple iOS<16.1
16.1
Apple iPadOS<16
16
Apple iOS<15.7.1
15.7.1
Apple iPadOS<15.7.1
15.7.1
Apple iPadOS<15.7.1
Apple iPhone OS<15.7.1
Apple macOS>=11.0<11.7.1
Apple macOS>=12.0<12.6.1
Apple tvOS<16.1
Apple WatchOS<9.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Apple macOS to a version that resolves this vulnerability.

    Fixed in 11.7.1
  2. Upgrade

    Upgrade tvOS to a version that resolves this vulnerability.

    Fixed in 16.1
  3. Upgrade

    Upgrade Apple iOS, iPadOS, and watchOS to a version that resolves this vulnerability.

    Fixed in 9.1
  4. Upgrade

    Upgrade macOS to a version that resolves this vulnerability.

    Fixed in 12.6.1
  5. Upgrade

    Upgrade macOS Ventura to a version that resolves this vulnerability.

    Fixed in 13
  6. Upgrade

    Upgrade Apple iOS and iPadOS to a version that resolves this vulnerability.

    Fixed in 16.1
  7. Upgrade

    Upgrade Apple iOS, iPadOS, and macOS to a version that resolves this vulnerability.

    Fixed in 16
  8. Upgrade

    Upgrade Apple iOS and iPadOS to a version that resolves this vulnerability.

    Fixed in 15.7.1
  9. Upgrade

    Upgrade Apple iOS, iPadOS, and macOS to a version that resolves this vulnerability.

    Fixed in 15.7.1
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in tvOS 16.1
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in iOS 15.7.1
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in iPadOS 15.7.1
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in macOS Ventura 13
  14. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in watchOS 9.1
  15. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in iOS 16.1
  16. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in iPadOS 16
  17. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in macOS Monterey 12.6.1
  18. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in macOS Big Sur 11.7.1
  19. Configuration

    Apply the vendor fix that addresses the code signature validation issue with improved checks.

    code signature validation access restrictions / improved checks (unspecified) = enabled
  20. Configuration

    Apply the vendor fix that addresses the access issue by adding additional sandbox restrictions.

    sandboxing additional sandbox restrictions = applied
  21. Configuration

    Apply the vendor fix that addresses the access issue with improved access restrictions.

    access control access restrictions (unspecified) = improved
  22. Configuration

    Apply the vendor fix that addresses the issue by removing additional entitlements.

    entitlements vulnerable entitlement set = reduced
  23. Configuration

    Apply the vendor fix that addresses the issue by removing the vulnerable code.

    vulnerable code removal = removed
  24. Configuration

    Apply the vendor fix that addresses the issue by improving handling of caches.

    caches cache handling = improved
  25. Configuration

    Apply the vendor fix that addresses the issue by improving memory handling.

    memory handling memory handling = improved
  26. Configuration

    Apply the vendor fix that addresses the logic/state issues with improved state management.

    state management state management = improved
  27. Configuration

    Apply the vendor fix that addresses the memory corruption issue with improved state management.

    memory corruption state management (for memory corruption) = improved

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.

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 vulnerability ID?

The vulnerability ID is CVE-2022-42798.

2

What is the title of the vulnerability?

The title of the vulnerability is 'Audio. The issue was addressed with improved memory handling.'

3

Which software versions are affected by CVE-2022-42798?

The affected software versions include Apple iOS up to version 16.1, Apple iPadOS up to version 16, Apple macOS Monterey up to version 12.6.1, Apple macOS Big Sur up to version 11.7.1, Apple iOS up to version 15.7.1, Apple iPadOS up to version 15.7.1, macOS Ventura up to version 13, Apple tvOS up to version 16.1, and Apple watchOS up to version 9.1.

4

How was CVE-2022-42798 addressed?

CVE-2022-42798 was addressed with improved memory handling.

5

Where can I find more information about CVE-2022-42798?

You can find more information about CVE-2022-42798 on the following references: [link 1](https://support.apple.com/en-us/HT213494), [link 2](https://support.apple.com/en-us/HT213489), [link 3](https://support.apple.com/en-us/HT213491).

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