|
CVE-2022-42826
|
2023-02-27 |
|
A use after free issue was addressed with...... |
|
431
|
|
CVE-2022-42837
|
2022-12-15 |
|
An issue existed in the parsing of URLs....... |
|
558
|
|
CVE-2022-42840
|
2022-12-15 |
|
The issue was addressed with improved memory... |
|
453
|
|
CVE-2022-42846
|
2022-12-15 |
|
The issue was addressed with improved memory... |
|
378
|
|
CVE-2022-42848
|
2022-12-15 |
|
A logic issue was addressed with improved checks....... |
|
344
|
|
CVE-2022-42852
|
2022-12-15 |
|
The issue was addressed with improved memory... |
|
452
|
|
CVE-2022-42855
|
2022-12-15 |
|
A logic issue was addressed with improved state...... |
|
425
|
|
CVE-2022-42856
|
2022-12-15 |
|
A type confusion issue was addressed with... |
|
502
|
|
CVE-2022-42861
|
2022-12-15 |
|
This issue was addressed with improved checks.... |
|
385
|
|
CVE-2022-42863
|
2022-12-15 |
|
A memory corruption issue was addressed with... |
|
443
|
