CVE-2024-40789: Input Validation
Accounts. The issue was addressed with improved checks.
Other sources
AirDrop. This issue was addressed through improved state management.
— Apple
An out-of-bounds access issue was addressed with improved bounds checking. This issue is fixed in iOS 16.7.9 and iPadOS 16.7.9, Safari 17.6, iOS 17.6 and iPadOS 17.6, watchOS 10.6, tvOS 17.6, visionOS 1.3, macOS Sonoma 14.6. Processing maliciously crafted web content may lead to an unexpected process crash.
— Debian
An out-of-bounds access issue was addressed with improved bounds checking. This issue is fixed in Safari 17.6, iOS 16.7.9 and iPadOS 16.7.9, iOS 17.6 and iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, visionOS 1.3, watchOS 10.6. Processing maliciously crafted web content may lead to an unexpected process crash.
— MITRE
apache. This is a vulnerability in open source code and Apple Software is among the affected projects. The CVE-ID was assigned by a third party. Learn more about the issue and CVE-ID at cve.org.
— Apple
APFS. The issue was addressed with improved restriction of data container access.
— Apple
Credit
Affected Software
Event History
Parent advisories
This vulnerability appears in the following advisories.
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2024-40804
- CVE-2023-38709
- CVE-2024-24795
- CVE-2024-27316
- CVE-2024-40783
- CVE-2024-40774
- CVE-2024-40814
- CVE-2024-40775
- CVE-2024-27877
- CVE-2024-27878
- CVE-2024-40799
- CVE-2024-27873
- CVE-2024-2004
- CVE-2024-2379
- CVE-2024-2398
- CVE-2024-2466
- CVE-2024-40827
- CVE-2024-40815
- CVE-2024-40795
- CVE-2023-6277
- CVE-2023-52356
- CVE-2024-40806
- CVE-2024-40777
- CVE-2024-40784
- CVE-2024-27863
- CVE-2024-40816
- CVE-2024-40788
- CVE-2024-40803
- CVE-2024-40805
- CVE-2024-40832
- CVE-2024-40796
- CVE-2024-6387
- CVE-2024-40781
- CVE-2024-40802
- CVE-2024-40823
- CVE-2024-27882
- CVE-2024-27883
- CVE-2024-40778
- CVE-2024-40800
- CVE-2023-27952
- CVE-2024-40817
- CVE-2024-40824
- CVE-2024-27871
- CVE-2024-27881
- CVE-2024-40821
- CVE-2024-40798
- CVE-2024-27872
- CVE-2024-27862
- CVE-2024-40833
- CVE-2024-40835
- CVE-2024-40836
- CVE-2024-40807
- CVE-2024-40834
- CVE-2024-40809
- CVE-2024-40812
- CVE-2024-40787
- CVE-2024-40793
- CVE-2024-40818
- CVE-2024-40822
- CVE-2024-40828
- CVE-2024-40811
- CVE-2024-40776
- CVE-2024-40782
- CVE-2024-40779
- CVE-2024-40780
- CVE-2024-40785
- CVE-2024-40789
- CVE-2024-4558
- CVE-2024-40794
- CVE-2024-40813
- CVE-2024-40829
- CVE-2024-27826
- CVE-2024-27804
- CVE-2024-27823
- CVE-2024-54551
- CVE-2024-44185
- CVE-2024-44206
- CVE-2024-54564
- CVE-2024-40786
- CVE-2024-44205
- CVE-2024-44306
- CVE-2024-44307
- CVE-2024-44141
- CVE-2024-44199
- CVE-2024-40810
- CVE-2024-44305
- CVE-2024-40865
Frequently Asked Questions
What is the severity of CVE-2024-40789?
CVE-2024-40789 is classified as a significant security vulnerability due to the potential for out-of-bounds access leading to unexpected behavior.
How do I fix CVE-2024-40789?
To address CVE-2024-40789, upgrade to the latest versions of the affected Apple products including iOS 16.7.9, iPadOS 16.7.9, Safari 17.6, and other relevant updates.
Which products are affected by CVE-2024-40789?
CVE-2024-40789 affects various Apple products including iOS, iPadOS, Safari, tvOS, watchOS, and macOS versions prior to the fixed releases.
What kind of issues can CVE-2024-40789 cause?
CVE-2024-40789 could allow maliciously crafted web content to lead to unexpected processing, potentially compromising user security.
Is there a specific version requirement to resolve CVE-2024-40789?
Yes, the specific version requirements to resolve CVE-2024-40789 include updating to iOS 16.7.9, iPadOS 16.7.9, Safari 17.6, and similar versions for other affected products.