Skip to content

Use after free in Animation

High severity GitHub Reviewed Published Feb 18, 2022 in cefsharp/CefSharp • Updated Feb 3, 2023

Package

nuget CefSharp.Common (NuGet)

Affected versions

<= 98.1.190

Patched versions

98.1.210
nuget CefSharp.Common.NETCore (NuGet)
<= 98.1.190
98.1.210
nuget CefSharp.OffScreen (NuGet)
<= 98.1.190
98.1.210
nuget CefSharp.OffScreen.NETCore (NuGet)
<= 98.1.190
98.1.210
nuget CefSharp.WinForms (NuGet)
<= 98.1.190
98.1.210
nuget CefSharp.WinForms.NETCore (NuGet)
<= 98.1.190
98.1.210
nuget CefSharp.Wpf (NuGet)
<= 98.1.190
98.1.210
nuget CefSharp.Wpf.HwndHost (NuGet)
<= 98.1.190
98.1.210
nuget CefSharp.Wpf.NETCore (NuGet)
<= 98.1.190
98.1.210

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.

References

@amaitland amaitland published to cefsharp/CefSharp Feb 18, 2022
Published to the GitHub Advisory Database Feb 22, 2022
Reviewed Feb 22, 2022
Published by the National Vulnerability Database Apr 5, 2022
Last updated Feb 3, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(97th percentile)

Weaknesses

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. Learn more on MITRE.

CVE ID

CVE-2022-0609

GHSA ID

GHSA-vv6j-ww6x-54gx

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.