A use-after-free issue was addressed with improved memory management. This issue is fixed in tvOS 17, iOS 17 and iPadOS 17, watchOS 10, macOS Ventura 13.6. An app may be able to execute arbitrary code with kernel privileges.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Link | Tags |
---|---|
https://support.apple.com/en-us/HT213938 | release notes vendor advisory |
https://support.apple.com/en-us/HT213931 | release notes vendor advisory |
https://support.apple.com/en-us/HT213936 | release notes vendor advisory |
https://support.apple.com/en-us/HT213937 | release notes vendor advisory |
http://seclists.org/fulldisclosure/2023/Oct/5 | third party advisory mailing list |
http://seclists.org/fulldisclosure/2023/Oct/10 | third party advisory mailing list |
http://seclists.org/fulldisclosure/2023/Oct/8 | |
http://seclists.org/fulldisclosure/2023/Oct/9 |