CVE-2024-23257: Buffer Overflow

Published Mar 5, 2024
·
Updated

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

Other sources

Accessibility. This issue was addressed with additional entitlement checks.

Apple

Admin Framework. A logic issue was addressed with improved checks.

Apple

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

Apple

AppKit. A logic issue was addressed with improved restrictions.

Apple

AppleMobileFileIntegrity. A downgrade issue affecting Intel-based Mac computers was addressed with additional code-signing restrictions.

Apple

Credit

Junsung Lee(Trend Micro Zero Day Initiative), an anonymous researcher, Zhenjiang Zhao(pangu team), Qianxin(CrowdStrike Counter Adversary Operations), (CrowdStrike Counter Adversary Operations), Amir Bazine(CrowdStrike Counter Adversary Operations), Karsten König(CrowdStrike Counter Adversary Operations), Dohyun Lee@@l33d0hyun, Lyutoon, Mr.R, Murray Mike, Pedro Tôrres@@t0rr3sp3dr0, CVE-2024-23235, Xinru Chi(Pangu Lab), CVE-2024-23225, koocola, ali yabuz, Kirin@@Pwnrin, Meysam Firouzi@@R00tkitsmm(Trend Micro Zero Day Initiative), @@08Tc3wBB(Jamf), CVE-2024-23283, Mickey Jin@@patch1t, CVE-2023-48795, CVE-2023-51384, CVE-2023-51385, Bohdan Stasiuk@@Bohdan_Stasiuk, Harsh Tyagi, Wojciech Regula(SecuRing), CVE-2024-23296, Lyra Rebane (rebane2001), Matej Rabzelj, CVE-2024-23238, Yiğit Can YILMAZ@@yilmazcanyigit, luckyu@@uuulucky, K宝(Fudan University), LFY@@secsys(Fudan University), Lewis Hardy, Bistrit Dahal, CVE-2024-23241, CVE-2024-23242, Joshua Jewett@@JoshJewett33, Matthew Loewen, Deutsche Telekom Security GmbH sponsored by Bundesamt für Sicherheit in der Informationstechnik, anbu1024(SecANT), Pwn2car, James Lee@@Windowsrcer, Johan Carlsson (joaxcar), Georg Felber, Marco Squarcina, m4yfly with TianGong Team(Legendsec at Qi'anxin Group), Guilherme Rambo(Best Buddy Apps), Csaba Fitzl@@theevilbit(OffSec), CVE-2024-23205, CVE-2022-48554, Marc Newlin(SkySafe), Brian McNulty, Stephan Casas, CVE-2024-23291, Clemens Lang, Koh M. Nakagawa(FFRI Security Inc), Meng Zhang (鲸落)(NorthSea), Jubaer Alnazi@@h33tjubaer, Csaba Fitzl@@theevilbit(Offensive Security), Patrick Reardon, CVE-2024-23220

Affected Software

12 affected componentsFixes available
Apple macOS<14.4
14.4
Apple visionOS<1.1
1.1
macOS<12.7.4
12.7.4
macOS Ventura<13.6.5
13.6.5
Apple iOS and iPadOS<16.7.6
16.7.6
Apple iOS, iPadOS, and macOS<16.7.6
16.7.6
Apple iOS, iPadOS, and macOS<16.7.6
iPhone OS<16.7.6
macOS>=12.0<12.7.4
macOS>=13.0<13.6.5
macOS>=14.0<14.4
Apple visionOS<1.1

Event History

Mar 7, 2024
Data Sourced
via Apple·12:00 AM
DescriptionWeaknessAffected Software
Updated
via Apple·12:00 AM
DescriptionWeakness
Mar 8, 2024
CVE Published
via MITRE·01:35 AM
Data Sourced
via MITRE·01:35 AM
DescriptionWeakness
Data Sourced
via NVD·02:15 AM
DescriptionSeverityWeaknessAffected Software
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-2024-23257?

The severity of CVE-2024-23257 is high due to the potential for memory handling vulnerabilities affecting various Apple operating systems.

2

How do I fix CVE-2024-23257?

To fix CVE-2024-23257, upgrade your Apple device to the latest versions: macOS Monterey 12.7.4, macOS Ventura 13.6.5, macOS Sonoma 14.4, visionOS 1.1, iOS 16.7.6, or iPadOS 16.7.6.

3

Which Apple products are affected by CVE-2024-23257?

CVE-2024-23257 affects Apple devices running iOS, iPadOS, visionOS, and various versions of macOS, specifically prior to the mentioned fixes.

4

What kind of exploitation can occur due to CVE-2024-23257?

Exploitation of CVE-2024-23257 could lead to the disclosure of potentially sensitive information through improper memory management when processing images.

5

When was CVE-2024-23257 disclosed?

CVE-2024-23257 was disclosed in early 2024, and updates were released shortly thereafter to address the vulnerability.

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