Summary
CefSharp affected by heap buffer overflow in WebP
Google is aware that an exploit for CVE-2023-4863 exists in the wild.
Description
Heap buffer overflow in WebP in Google Chrome prior to 116.0.5845.187 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: Critical)
References
- https://www.cve.org/CVERecord?id=CVE-2023-4863
- https://nvd.nist.gov/vuln/detail/CVE-2023-4863
- https://www.techtarget.com/searchsecurity/news/366551978/Browser-companies-patch-critical-zero-day-vulnerability
Updated
There is another related security vulnerability.
There's another related CVE (CVE-2023-5217) that is fixed in Chromium 117.0.5938.132. This one is triggered by WebCodecs API encoder usage, so a workaround for older versions is to disable the WebCodecs API (--disable-blink-features=WebCodecs).
As per https://magpcss.org/ceforum/viewtopic.php?f=6&t=19551#p54150
Impact
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 116.0.230 or later; CefSharp.Common.NETCore to 116.0.230 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-J646-GJ5P-P45G? GHSA-J646-GJ5P-P45G is a critical-severity security vulnerability in CefSharp.Common (nuget), affecting versions < 116.0.230. It is fixed in 116.0.230.
- Which packages are affected by GHSA-J646-GJ5P-P45G?
CefSharp.Common(nuget) (versions < 116.0.230)CefSharp.Common.NETCore(nuget) (versions < 116.0.230)
- Is there a fix for GHSA-J646-GJ5P-P45G? Yes. GHSA-J646-GJ5P-P45G is fixed in 116.0.230. Upgrade to this version or later.
- Is GHSA-J646-GJ5P-P45G exploitable, and should I be worried? Whether GHSA-J646-GJ5P-P45G 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 GHSA-J646-GJ5P-P45G 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 GHSA-J646-GJ5P-P45G?
- Upgrade
CefSharp.Commonto 116.0.230 or later - Upgrade
CefSharp.Common.NETCoreto 116.0.230 or later
- Upgrade