CVE-2022-34491
Unknown
Last modified
This CVE is reserved or rejected; no details have been published by NVD.
Description
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2022-29969. Reason: This candidate is a duplicate of CVE-2022-29969. A typo caused the wrong ID to be used. Notes: All CVE users should reference CVE-2022-29969 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage
Timeline
- Published
- Last Modified
- Status
- Rejected
Related CVEs from 2022
- CVE-2022-34485Mozilla developers Bryce Seager van Dyk and the Mozilla Fuzz…9.8
- CVE-2022-34486Path traversal vulnerability in PukiWiki versions 1.4.5 to 1…7.2
- CVE-2022-34487Unauthenticated Arbitrary Option Update vulnerability in bip…5.3
- CVE-2022-34488Improper buffer restrictions in the firmware for some Intel(…7.8
- CVE-2022-34489Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2022-3449Use after free in Safe Browsing in Google Chrome prior to 10…8.8
- CVE-2022-34494rpmsg_virtio_add_ctrl_dev in drivers/rpmsg/virtio_rpmsg_bus.…5.5
- CVE-2022-34495rpmsg_probe in drivers/rpmsg/virtio_rpmsg_bus.c in the Linux…5.5
- CVE-2022-34496Hiby R3 PRO firmware v1.5 to v1.7 was discovered to contain …9.8
- CVE-2022-3450Use after free in Peer Connection in Google Chrome prior to …8.8
- CVE-2022-34500The bin-collect package in PyPI before v0.1 included a code …9.8
- CVE-2022-34501The bin-collection package in PyPI before v0.1 included a co…9.8
Are you affected by CVE-2022-34491?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
