| CVE-2022-22665 |
A logic issue was addressed with improved validation
|
Non notée
|
18 mars 2022 |
| CVE-2022-22651 |
An out-of-bounds write issue was addressed with improved bounds checking
|
Non notée
|
18 mars 2022 |
| CVE-2022-22656 |
An authentication issue was addressed with improved state management
|
Non notée
|
18 mars 2022 |
| CVE-2022-22664 |
An out-of-bounds read was addressed with improved bounds checking
|
Non notée
|
18 mars 2022 |
| CVE-2022-22657 |
A memory initialization issue was addressed with improved memory handling
|
Non notée
|
18 mars 2022 |
| CVE-2022-22660 |
This issue was addressed with a new entitlement
|
Non notée
|
18 mars 2022 |
| CVE-2022-22648 |
This issue was addressed with improved checks
|
Non notée
|
18 mars 2022 |
| CVE-2022-22644 |
A privacy issue existed in the handling of Contact cards
|
Non notée
|
18 mars 2022 |
| CVE-2022-22647 |
This issue was addressed with improved checks
|
Non notée
|
18 mars 2022 |
| CVE-2022-22650 |
This issue was addressed with improved checks
|
Non notée
|
18 mars 2022 |
| CVE-2022-22638 |
A null pointer dereference was addressed with improved validation
|
Non notée
|
18 mars 2022 |
| CVE-2022-22640 |
A memory corruption issue was addressed with improved validation
|
Non notée
|
18 mars 2022 |
| CVE-2022-22641 |
A use after free issue was addressed with improved memory management
|
Non notée
|
18 mars 2022 |
| CVE-2022-22633 |
A memory corruption issue was addressed with improved state management
|
Non notée
|
18 mars 2022 |
| CVE-2022-22639 |
A logic issue was addressed with improved state management
|
Non notée
|
18 mars 2022 |
| CVE-2022-22631 |
An out-of-bounds write issue was addressed with improved bounds checking
|
Non notée
|
18 mars 2022 |
| CVE-2022-22632 |
A logic issue was addressed with improved state management
|
Non notée
|
18 mars 2022 |
| CVE-2022-22621 |
This issue was addressed with improved checks
|
Non notée
|
18 mars 2022 |
| CVE-2022-22626 |
An out-of-bounds read was addressed with improved bounds checking
|
Non notée
|
18 mars 2022 |
| CVE-2022-22627 |
An out-of-bounds read was addressed with improved bounds checking
|
Non notée
|
18 mars 2022 |
| CVE-2022-22625 |
An out-of-bounds read was addressed with improved input validation
|
Non notée
|
18 mars 2022 |
| CVE-2022-22620 |
Exploitée
Apple iOS, iPadOS, and macOS Webkit Use-After-Free Vulnerability
|
8.8
Élevée
|
18 mars 2022 |
| CVE-2022-22612 |
A memory consumption issue was addressed with improved memory handling
|
Non notée
|
18 mars 2022 |
| CVE-2022-22614 |
A use after free issue was addressed with improved memory management
|
Non notée
|
18 mars 2022 |
| CVE-2022-22609 |
The issue was addressed with additional permissions checks
|
Non notée
|
18 mars 2022 |