Skip to content

GHSA-vv6j-ww6x-54gx CVE-2022-0609

Use after free in Animation

High Known exploited NuGet
Severity
8.8 / 10
High · CVSS 3.1
Exploit chance (EPSS)
22.44%
Chance of exploitation in the next 30 days. Higher than 97.70% of scored vulnerabilities.
Known exploited
Yes
In CISA's catalog since Feb 15, 2022
Weakness
CWE-416 Use After Free
Fix
Available
9 packages have a fixed version
Exploited in the wild. Google Chromium Animation Use-After-Free Vulnerability (Google Chromium Animation). Required action: Apply updates per vendor instructions. Due for U.S. federal agencies by Mar 1, 2022.

Description

CVE-2022-0609: Use after free in Animation

Google is aware of reports that exploits for CVE-2022-0609 exist in the wild.

The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are unknown but an exploit is available.

There is currently little other public information on the issue other than it has been flagged as High severity.

Affected versions

NuGet

PackageVulnerableFixed in
CefSharp.Common
< 98.1.210
98.1.210
CefSharp.Common.NETCore
< 98.1.210
98.1.210
CefSharp.OffScreen
< 98.1.210
98.1.210
CefSharp.OffScreen.NETCore
< 98.1.210
98.1.210
CefSharp.WinForms
< 98.1.210
98.1.210
CefSharp.WinForms.NETCore
< 98.1.210
98.1.210
CefSharp.Wpf
< 98.1.210
98.1.210
CefSharp.Wpf.HwndHost
< 98.1.210
98.1.210
CefSharp.Wpf.NETCore
< 98.1.210
98.1.210

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

CefSharp.Common NuGet → 98.1.210

dotnet
dotnet add package CefSharp.Common --version 98.1.210

CefSharp.Common.NETCore NuGet → 98.1.210

dotnet
dotnet add package CefSharp.Common.NETCore --version 98.1.210

CefSharp.OffScreen NuGet → 98.1.210

dotnet
dotnet add package CefSharp.OffScreen --version 98.1.210

CefSharp.OffScreen.NETCore NuGet → 98.1.210

dotnet
dotnet add package CefSharp.OffScreen.NETCore --version 98.1.210

CefSharp.WinForms NuGet → 98.1.210

dotnet
dotnet add package CefSharp.WinForms --version 98.1.210

CefSharp.WinForms.NETCore NuGet → 98.1.210

dotnet
dotnet add package CefSharp.WinForms.NETCore --version 98.1.210

CefSharp.Wpf NuGet → 98.1.210

dotnet
dotnet add package CefSharp.Wpf --version 98.1.210

CefSharp.Wpf.HwndHost NuGet → 98.1.210

dotnet
dotnet add package CefSharp.Wpf.HwndHost --version 98.1.210

CefSharp.Wpf.NETCore NuGet → 98.1.210

dotnet
dotnet add package CefSharp.Wpf.NETCore --version 98.1.210

Severity breakdown

CVSS 3.1 8.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-416: Use After Free

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.

How to prevent it
  • 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.

References

Timeline

  1. Added to CISA's Known Exploited Vulnerabilities catalog
  2. Published
  3. Remediation due for U.S. federal agencies
  4. Last updated by the source
  5. Latest EPSS score
AdvisorySeverityWhy it's related
CVE-2020-16017
Use after free in CefSharp
Critical Known exploited Also affects CefSharp.Common
CVE-2020-16013
Inappropriate implementation in V8 in CefSharp
High Known exploited Also affects CefSharp.Common
CVE-2020-16009
Inappropriate implementation in V8
High Known exploited Also affects CefSharp.Common
CVE-2020-15999
Heap buffer overflow in CefSharp
Critical Known exploited Also affects CefSharp.Common
CVE-2026-109619
PHP has various global state that temporarily points into request memory.
Critical Known exploited Same weakness, CWE-416
CVE-2026-109618
PHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request.
Critical Known exploited Same weakness, CWE-416
GHSA-7mwm-ghpf-9vrm
Pillow: Double free in ImagingScaleAffine on calloc failure via Image.transform
High Same weakness, CWE-416
GHSA-4rr5-89j8-mwwm
Pillow: Heap use-after-free when encoding TIFF to an in-memory buffer
High Same weakness, CWE-416
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor