This issue was addressed with improved checks. This issue is fixed in iOS 12.4, macOS Mojave 10.14.6, tvOS 12.4, watchOS 5.3. An attacker may be able to trigger a use-after-free in an application deserializing an untrusted NSDictionary.
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.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Iphone_os | Apple | * | 12.4 (excluding) |
| Mac_os_x | Apple | * | 10.14.6 (excluding) |
| Tvos | Apple | * | 12.4 (excluding) |
| Watchos | Apple | * | 5.3 (excluding) |