CyberSecBulletin

Use After Free

CWE-416

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

We track 4,465 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 8.3. 109 have been exploited in real attacks.

How this weakness is prevented

  • Architecture and Design: Choose a language that provides automatic memory management.
  • Implementation: When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.

Latest Use After Free vulnerabilities

  • 7.8 High severity

    kernel: Use After Free

    CVE-2022-1158Kernel

    A flaw was found in KVM. When updating a guest's page table entry, vm_pgoff was improperly used as the offset to get the page's pfn. As vaddr and vm_pgoff are controllable by user-mode processes, this flaw allows unprivileged local users on the host to write o

  • 8.1 High severity

    Connman: Use After Free

    CVE-2022-32293IntelEPSS 2.05%

    In ConnMan through 1.41, a man-in-the-middle attack against a WISPR HTTP query could be used to trigger a use-after-free in WISPR handling, leading to crashes or code execution.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-2399Google

    Use after free in WebGPU in Google Chrome prior to 100.0.4896.88 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-2481GoogleEPSS 1.21%

    Use after free in Views in Google Chrome prior to 103.0.5060.134 allowed a remote attacker who convinced a user to engage in specific user interactions to potentially exploit heap corruption via UI interaction.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-2480GoogleEPSS 18.8%

    Use after free in Service Worker API in Google Chrome prior to 103.0.5060.134 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-2478Google

    Use after free in PDF in Google Chrome prior to 103.0.5060.134 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-2477Google

    Use after free in Guest View in Google Chrome prior to 103.0.5060.134 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a crafted HTML page.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-2296GoogleEPSS 1.15%

    Use after free in Chrome OS Shell in Google Chrome on Chrome OS prior to 103.0.5060.114 allowed a remote attacker who convinced a user to engage in specific user interactions to potentially exploit heap corruption via direct UI interactions.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-2163Google

    Use after free in Cast UI and Toolbar in Google Chrome prior to 103.0.5060.134 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via UI interaction.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-2161GoogleEPSS 1.01%

    Use after free in WebApp Provider in Google Chrome prior to 103.0.5060.53 allowed a remote attacker who convinced the user to engage in specific user interactions to potentially exploit heap corruption via specific UI interactions.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-2158GoogleEPSS 1.06%

    Type confusion in V8 in Google Chrome prior to 103.0.5060.53 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-2157GoogleEPSS 1.03%

    Use after free in Interest groups in Google Chrome prior to 103.0.5060.53 allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-2156GoogleEPSS 1.52%

    Use after free in Core in Google Chrome prior to 103.0.5060.53 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-2011GoogleEPSS 1.11%

    Use after free in ANGLE in Google Chrome prior to 102.0.5005.115 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-2007GoogleEPSS 1.05%

    Use after free in WebGPU in Google Chrome prior to 102.0.5005.115 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1919GoogleEPSS 1.38%

    Use after free in Codecs in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1870Google

    Use after free in App Service in Google Chrome prior to 102.0.5005.61 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a crafted Chrome Extension.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1866Google

    Use after free in Tablet Mode in Google Chrome on Chrome OS prior to 102.0.5005.61 allowed a remote attacker who convinced a user to engage in specific user interactions to potentially exploit heap corruption via specific user interactions.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1865Google

    Use after free in Bookmarks in Google Chrome prior to 102.0.5005.61 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a crafted Chrome Extension and specific user interaction.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1864Google

    Use after free in WebApp Installs in Google Chrome prior to 102.0.5005.61 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a crafted Chrome Extension and specific user interaction.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1863Google

    Use after free in Tab Groups in Google Chrome prior to 102.0.5005.61 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a crafted Chrome Extension and specific user interaction.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1861Google

    Use after free in Sharing in Google Chrome on Chrome OS prior to 102.0.5005.61 allowed a remote attacker who convinced a user to enage in specific user interactions to potentially exploit heap corruption via specific user interaction.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1860Google

    Use after free in UI Foundations in Google Chrome on Chrome OS prior to 102.0.5005.61 allowed a remote attacker who convinced a user to engage in specific user interaction to potentially exploit heap corruption via specific user interactions.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1859Google

    Use after free in Performance Manager in Google Chrome prior to 102.0.5005.61 allowed a remote attacker who convinced a user to engage in specific user interaction to potentially exploit heap corruption via a crafted HTML page.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1856Google

    Use after free in User Education in Google Chrome prior to 102.0.5005.61 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a crafted Chrome Extension or specific user interaction.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1855Google

    Use after free in Messaging in Google Chrome prior to 102.0.5005.61 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1854Google

    Use after free in ANGLE in Google Chrome prior to 102.0.5005.61 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • 9.6 Critical severity

    Chrome: Use After Free

    CVE-2022-1853GoogleEPSS 1.07%

    Use after free in Indexed DB in Google Chrome prior to 102.0.5005.61 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1641Google

    Use after free in Web UI Diagnostics in Google Chrome on Chrome OS prior to 101.0.4951.64 allowed a remote attacker who convinced a user to engage in specific UI interactions to potentially exploit heap corruption via specific user interaction.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1640Google

    Use after free in Sharing in Google Chrome prior to 101.0.4951.64 allowed a remote attacker who convinced a user to engage in specific UI interactions to potentially exploit heap corruption via a crafted HTML page.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1639Google

    Use after free in ANGLE in Google Chrome prior to 101.0.4951.64 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1636Google

    Use after free in Performance APIs in Google Chrome prior to 101.0.4951.64 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1635Google

    Use after free in Permission Prompts in Google Chrome prior to 101.0.4951.64 allowed a remote attacker who convinced a user to engage in specific UI interactions to potentially exploit heap corruption via specific user interactions.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1634Google

    Use after free in Browser UI in Google Chrome prior to 101.0.4951.64 allowed a remote attacker who had convinced a user to engage in specific UI interaction to potentially exploit heap corruption via specific user interactions.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1633Google

    Use after free in Sharesheet in Google Chrome on Chrome OS prior to 101.0.4951.64 allowed a remote attacker who convinced a user to engage in specific UI interactions to potentially exploit heap corruption via specific user interactions.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1496Google

    Use after free in File Manager in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to potentially exploit heap corruption via specific and direct user interaction.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1493Google

    Use after free in Dev Tools in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to potentially exploit heap corruption via specific and direct user interaction.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1491Google

    Use after free in Bookmarks in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to potentially exploit heap corruption via specific and direct user interaction.

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2022-1490Google

    Use after free in Browser Switcher in Google Chrome prior to 101.0.4951.41 allowed a remote attacker who convinced a user to engage in specific user interaction to potentially exploit heap corruption via a crafted HTML page.

  • 7.5 High severity

    Chrome: Use After Free

    CVE-2022-1487GoogleEPSS 1.16%

    Use after free in Ozone in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to potentially exploit heap corruption via running a Wayland test.