|
CVE-2022-42837
|
2022-12-15 |
|
An issue existed in the parsing of URLs....... |
|
586
|
|
CVE-2022-42842
|
2022-12-15 |
|
The issue was addressed with improved memory... |
|
531
|
|
CVE-2022-42843
|
2022-12-15 |
|
This issue was addressed with improved data... |
|
502
|
|
CVE-2022-42845
|
2022-12-15 |
|
The issue was addressed with improved memory... |
|
639
|
|
CVE-2022-42848
|
2022-12-15 |
|
A logic issue was addressed with improved checks....... |
|
363
|
|
CVE-2022-42849
|
2022-12-15 |
|
An access issue existed with privileged API... |
|
500
|
|
CVE-2022-42851
|
2022-12-15 |
|
The issue was addressed with improved memory... |
|
400
|
|
CVE-2022-42852
|
2022-12-15 |
|
The issue was addressed with improved memory... |
|
480
|
|
CVE-2022-42855
|
2022-12-15 |
|
A logic issue was addressed with improved state...... |
|
441
|
|
CVE-2022-42856
|
2022-12-15 |
|
A type confusion issue was addressed with... |
|
522
|
