# CVEs published 2022-02-12 24 CVEs were published on February 12, 2022: 0 critical, 2 high. Days are UTC. - [CVE-2022-0569](https://cve.now/CVE-2022-0569.md): Observable Discrepancy in snipe/snipe-it (CVSS 5.3, snipe/snipe-it) - [CVE-2022-0565](https://cve.now/CVE-2022-0565.md): Cross-site Scripting in pimcore/pimcore (CVSS 7.6, pimcore/pimcore) - [CVE-2022-22765](https://cve.now/CVE-2022-22765.md): BD Viper LT System - Hardcoded Credentials (CVSS 8.0, Becton Dickinson (BD) BD Viper LT System) - [CVE-2022-0311](https://cve.now/CVE-2022-0311.md): Heap 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 spec (no CVSS, Google Chrome) - [CVE-2022-0310](https://cve.now/CVE-2022-0310.md): Heap buffer overflow in Task Manager in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially exploit heap corruption (no CVSS, Google Chrome) - [CVE-2022-0309](https://cve.now/CVE-2022-0309.md): Inappropriate implementation in Autofill in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to bypass navigation restrictions (no CVSS, Google Chrome) - [CVE-2022-0308](https://cve.now/CVE-2022-0308.md): Use 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 engage (no CVSS, Google Chrome) - [CVE-2022-0307](https://cve.now/CVE-2022-0307.md): Use 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 spec (no CVSS, Google Chrome) - [CVE-2022-0306](https://cve.now/CVE-2022-0306.md): Heap buffer overflow in PDFium in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially exploit heap corruption via a (no CVSS, Google Chrome) - [CVE-2022-0305](https://cve.now/CVE-2022-0305.md): Inappropriate implementation in Service Worker API in Google Chrome prior to 97.0.4692.99 allowed a remote attacker who had compromised the (no CVSS, Google Chrome) - [CVE-2022-0304](https://cve.now/CVE-2022-0304.md): Use 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 user (no CVSS, Google Chrome) - [CVE-2022-0302](https://cve.now/CVE-2022-0302.md): Use 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 interac (no CVSS, Google Chrome) - [CVE-2022-0301](https://cve.now/CVE-2022-0301.md): Heap buffer overflow in DevTools in Google Chrome prior to 97.0.4692.99 allowed an attacker who convinced a user to install a malicious exte (no CVSS, Google Chrome) - [CVE-2022-0300](https://cve.now/CVE-2022-0300.md): Use 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 (no CVSS, Google Chrome) - [CVE-2022-0298](https://cve.now/CVE-2022-0298.md): Use after free in Scheduling in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially exploit heap corruption via a c (no CVSS, Google Chrome) - [CVE-2022-0297](https://cve.now/CVE-2022-0297.md): Use after free in Vulkan in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially exploit heap corruption via a craft (no CVSS, Google Chrome) - [CVE-2022-0296](https://cve.now/CVE-2022-0296.md): Use 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 use (no CVSS, Google Chrome) - [CVE-2022-0295](https://cve.now/CVE-2022-0295.md): Use 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 user (no CVSS, Google Chrome) - [CVE-2022-0294](https://cve.now/CVE-2022-0294.md): Inappropriate implementation in Push messaging in Google Chrome prior to 97.0.4692.99 allowed a remote attacker who had compromised the rend (no CVSS, Google Chrome) - [CVE-2022-0293](https://cve.now/CVE-2022-0293.md): Use after free in Web packaging in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially exploit heap corruption via (no CVSS, Google Chrome) - [CVE-2022-0292](https://cve.now/CVE-2022-0292.md): Inappropriate implementation in Fenced Frames in Google Chrome prior to 97.0.4692.99 allowed a remote attacker who had compromised the rende (no CVSS, Google Chrome) - [CVE-2022-0291](https://cve.now/CVE-2022-0291.md): Inappropriate implementation in Storage in Google Chrome prior to 97.0.4692.99 allowed a remote attacker who had compromised the renderer pr (no CVSS, Google Chrome) - [CVE-2022-0290](https://cve.now/CVE-2022-0290.md): Use after free in Site isolation in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially perform a sandbox escape vi (no CVSS, Google Chrome) - [CVE-2022-0289](https://cve.now/CVE-2022-0289.md): Use after free in Safe browsing in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially exploit heap corruption via (no CVSS, Google Chrome) --- Source: cve.now, built and run by Sazabi (AI-native observability and security) Page: https://cve.now/daily/2022-02-12 Site guide for agents: https://cve.now/llms.txt Uses NVD data; not endorsed by NVD.