Summary
Use after free in Animation
CVE-2022-0609: Use after free in Animation
- https://chromereleases.googleblog.com/2022/02/stable-channel-update-for-desktop_14.html
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0609
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.
Impact
Memory is accessed after it has been freed, leading to undefined behavior in native code. Typical impact: memory corruption, crash, or potential code execution.
CVE-2022-0609 has a CVSS score of 8.8 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (98.1.210); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
CefSharp.Common to 98.1.210 or later; CefSharp.OffScreen to 98.1.210 or later; CefSharp.WinForms to 98.1.210 or later; CefSharp.Wpf to 98.1.210 or later; CefSharp.Wpf.HwndHost to 98.1.210 or later; CefSharp.Common.NETCore to 98.1.210 or later; CefSharp.OffScreen.NETCore to 98.1.210 or later; CefSharp.WinForms.NETCore to 98.1.210 or later; CefSharp.Wpf.NETCore to 98.1.210 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2022-0609? CVE-2022-0609 is a high-severity use after free vulnerability in CefSharp.Common (nuget), affecting versions <= 98.1.190. It is fixed in 98.1.210. Memory is accessed after it has been freed, leading to undefined behavior in native code.
- How severe is CVE-2022-0609? CVE-2022-0609 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2022-0609?
CefSharp.Common(nuget) (versions <= 98.1.190)CefSharp.OffScreen(nuget) (versions <= 98.1.190)CefSharp.WinForms(nuget) (versions <= 98.1.190)CefSharp.Wpf(nuget) (versions <= 98.1.190)CefSharp.Wpf.HwndHost(nuget) (versions <= 98.1.190)CefSharp.Common.NETCore(nuget) (versions <= 98.1.190)CefSharp.OffScreen.NETCore(nuget) (versions <= 98.1.190)CefSharp.WinForms.NETCore(nuget) (versions <= 98.1.190)CefSharp.Wpf.NETCore(nuget) (versions <= 98.1.190)
- Is there a fix for CVE-2022-0609? Yes. CVE-2022-0609 is fixed in 98.1.210. Upgrade to this version or later.
- Is CVE-2022-0609 exploitable, and should I be worried? Whether CVE-2022-0609 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-0609 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-0609?
- Upgrade
CefSharp.Commonto 98.1.210 or later - Upgrade
CefSharp.OffScreento 98.1.210 or later - Upgrade
CefSharp.WinFormsto 98.1.210 or later - Upgrade
CefSharp.Wpfto 98.1.210 or later - Upgrade
CefSharp.Wpf.HwndHostto 98.1.210 or later - Upgrade
CefSharp.Common.NETCoreto 98.1.210 or later - Upgrade
CefSharp.OffScreen.NETCoreto 98.1.210 or later - Upgrade
CefSharp.WinForms.NETCoreto 98.1.210 or later - Upgrade
CefSharp.Wpf.NETCoreto 98.1.210 or later
- Upgrade