CVEs published February 12, 2022
24 CVEs were published on February 12, 2022: 0 critical, 2 high.
- Published
- 24
- Critical
- 0
- High
- 2
- Medium
- 1
- Low
- 0
- Unrated
- 21
- Now in CISA KEV
- 0
- Fix available
- 23
Most affected products
- Google Chrome
- 21
- Becton Dickinson (BD) BD Viper LT System
- 1
- pimcore/pimcore
- 1
- snipe/snipe-it
- 1
High 2
Medium, low and unrated 22
- CVE-2022-0569Observable Discrepancy in snipe/snipe-itsnipe/snipe-it
- CVE-2022-0311Heap buffer overflow in Task Manager in Google Chrome prior to 97.0.4692.99 allowed a remote attacker who convinced a user to engage in specGoogle Chrome
- CVE-2022-0310Heap buffer overflow in Task Manager in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially exploit heap corruptionGoogle Chrome
- CVE-2022-0309Inappropriate implementation in Autofill in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to bypass navigation restrictions Google Chrome
- CVE-2022-0308Use after free in Data Transfer in Google Chrome on Chrome OS prior to 97.0.4692.99 allowed a remote attacker who convinced a user to engageGoogle Chrome
- CVE-2022-0307Use after free in Optimization Guide in Google Chrome prior to 97.0.4692.99 allowed a remote attacker who convinced a user to engage in specGoogle Chrome
- CVE-2022-0306Heap buffer overflow in PDFium in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially exploit heap corruption via aGoogle Chrome
- CVE-2022-0305Inappropriate implementation in Service Worker API in Google Chrome prior to 97.0.4692.99 allowed a remote attacker who had compromised the Google Chrome
- CVE-2022-0304Use after free in Bookmarks in Google Chrome prior to 97.0.4692.99 allowed a remote attacker who convinced a user to engage in specific userGoogle Chrome
- CVE-2022-0302Use after free in Omnibox in Google Chrome prior to 97.0.4692.99 allowed an attacker who convinced a user to engage in specific user interacGoogle Chrome
- CVE-2022-0301Heap buffer overflow in DevTools in Google Chrome prior to 97.0.4692.99 allowed an attacker who convinced a user to install a malicious exteGoogle Chrome
- CVE-2022-0300Use after free in Text Input Method Editor in Google Chrome on Android prior to 97.0.4692.99 allowed a remote attacker who convinced a user Google Chrome
- CVE-2022-0298Use after free in Scheduling in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially exploit heap corruption via a cGoogle Chrome
- CVE-2022-0297Use after free in Vulkan in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially exploit heap corruption via a craftGoogle Chrome
- CVE-2022-0296Use after free in Printing in Google Chrome prior to 97.0.4692.99 allowed a remote attacker who convinced the user to engage is specific useGoogle Chrome
- CVE-2022-0295Use after free in Omnibox in Google Chrome prior to 97.0.4692.99 allowed a remote attacker who convinced the user to engage is specific userGoogle Chrome
- CVE-2022-0294Inappropriate implementation in Push messaging in Google Chrome prior to 97.0.4692.99 allowed a remote attacker who had compromised the rendGoogle Chrome
- CVE-2022-0293Use after free in Web packaging in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially exploit heap corruption via Google Chrome
- CVE-2022-0292Inappropriate implementation in Fenced Frames in Google Chrome prior to 97.0.4692.99 allowed a remote attacker who had compromised the rendeGoogle Chrome
- CVE-2022-0291Inappropriate implementation in Storage in Google Chrome prior to 97.0.4692.99 allowed a remote attacker who had compromised the renderer prGoogle Chrome
- CVE-2022-0290Use after free in Site isolation in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially perform a sandbox escape viGoogle Chrome
- CVE-2022-0289Use after free in Safe browsing in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially exploit heap corruption via Google Chrome