| CVE-2022-32814 |
A type confusion issue was addressed with improved state handling
|
7.8
High
|
Sep 23, 2022 |
| CVE-2022-32849 |
An information disclosure issue was addressed by removing the vulnerable code
|
5.5
Medium
|
Sep 23, 2022 |
| CVE-2022-32802 |
A logic issue was addressed with improved checks
|
7.8
High
|
Sep 20, 2022 |
| CVE-2022-32788 |
A buffer overflow was addressed with improved bounds checking
|
9.8
Critical
|
Sep 20, 2022 |
| CVE-2022-32857 |
This issue was addressed by using HTTPS when sending information over the network
|
4.3
Medium
|
Aug 24, 2022 |
| CVE-2022-32813 |
The issue was addressed with improved memory handling
|
7.8
High
|
Aug 24, 2022 |
| CVE-2022-32837 |
This issue was addressed with improved checks
|
7.8
High
|
Aug 24, 2022 |
| CVE-2022-32839 |
The issue was addressed with improved bounds checks
|
9.8
Critical
|
Aug 24, 2022 |
| CVE-2022-32793 |
Multiple out-of-bounds write issues were addressed with improved bounds checking
|
7.5
High
|
Aug 24, 2022 |
| CVE-2022-26740 |
An out-of-bounds write issue was addressed with improved bounds checking
|
Not rated
|
May 26, 2022 |
| CVE-2022-26739 |
An out-of-bounds write issue was addressed with improved bounds checking
|
Not rated
|
May 26, 2022 |
| CVE-2022-26738 |
An out-of-bounds write issue was addressed with improved bounds checking
|
Not rated
|
May 26, 2022 |
| CVE-2022-26737 |
An out-of-bounds write issue was addressed with improved bounds checking
|
Not rated
|
May 26, 2022 |
| CVE-2022-26736 |
An out-of-bounds write issue was addressed with improved bounds checking
|
Not rated
|
May 26, 2022 |
| CVE-2022-26724 |
An authentication issue was addressed with improved state management
|
Not rated
|
May 26, 2022 |
| CVE-2022-26701 |
A race condition was addressed with improved locking
|
Not rated
|
May 26, 2022 |
| CVE-2022-22670 |
An access issue was addressed with improved access restrictions
|
Not rated
|
Mar 18, 2022 |
| CVE-2022-22666 |
A memory corruption issue was addressed with improved validation
|
Not rated
|
Mar 18, 2022 |
| CVE-2022-22638 |
A null pointer dereference was addressed with improved validation
|
Not rated
|
Mar 18, 2022 |
| CVE-2022-22640 |
A memory corruption issue was addressed with improved validation
|
Not rated
|
Mar 18, 2022 |
| CVE-2022-22641 |
A use after free issue was addressed with improved memory management
|
Not rated
|
Mar 18, 2022 |
| CVE-2022-22635 |
An out-of-bounds write issue was addressed with improved bounds checking
|
Not rated
|
Mar 18, 2022 |
| CVE-2022-22636 |
An out-of-bounds write issue was addressed with improved bounds checking
|
Not rated
|
Mar 18, 2022 |
| CVE-2022-22632 |
A logic issue was addressed with improved state management
|
Not rated
|
Mar 18, 2022 |
| CVE-2022-22634 |
A buffer overflow was addressed with improved bounds checking
|
Not rated
|
Mar 18, 2022 |