How severe is GHSA-4c29-gfrp-g6x9?

No CVSS score has been assigned to GHSA-4c29-gfrp-g6x9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4c29-gfrp-g6x9?

GHSA-4c29-gfrp-g6x9 affects the following packages: CefSharp.Common (NuGet), CefSharp.Common.NETCore (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-4c29-gfrp-g6x9?

Update CefSharp.Common to 117.2.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4c29-gfrp-g6x9 is resolved across your whole dependency graph.

How do I detect GHSA-4c29-gfrp-g6x9 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for CefSharp.Common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-4c29-gfrp-g6x9 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-4c29-gfrp-g6x9?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4c29-gfrp-g6x9 can be triaged on real exposure rather than presence alone.

Is GHSA-4c29-gfrp-g6x9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4c29-gfrp-g6x9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-4c29-gfrp-g6x9 published, and has it been updated?

GHSA-4c29-gfrp-g6x9 was published on October 5, 2023 and was last updated on November 30, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

Not in CISA KEV

GHSA-4c29-gfrp-g6x9 — CefSharp.Common

Fix: cefsharp/CefSharp@45e66f7

GHSA-4c29-gfrp-g6x9 is a remote code execution vulnerability in CefSharp.Common. A fix is available for CefSharp.Common — see the affected versions and patch details below.

CefSharp affected by libvpx's heap buffer overflow in vp8 encoding

Published

Oct 5, 2023

Updated

Nov 30, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 30, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

.NETCefSharp.Common.NETCefSharp.Common.NETCore

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Google is aware that an exploit for CVE-2023-5217 exists in the wild.

Description Heap buffer overflow in vp8 encoding in libvpx in Google Chrome prior to 117.0.5938.132 and libvpx 1.13.1 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

References

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`CefSharp.Common`	all versions	117.2.20`dotnet add package CefSharp.Common --version 117.2.20`
.NETNuGet	`CefSharp.Common.NETCore`	all versions	117.2.20`dotnet add package CefSharp.Common.NETCore --version 117.2.20`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for CefSharp.Common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update CefSharp.Common to 117.2.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4c29-gfrp-g6x9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4c29-gfrp-g6x9 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-4c29-gfrp-g6x9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Google is aware that an exploit for CVE-2023-5217 exists in the wild. Description Heap buffer overflow in vp8 encoding in libvpx in Google Chrome prior to 117.0.5938.132 and libvpx 1.13.1 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High) References - https://www.cve.org/CVERecord?id=CVE-2023-5217 - https://nvd.nist.gov/vuln/detail/CVE-2023-5217

O3 Security · Impact-Aware SCA

Is GHSA-4c29-gfrp-g6x9 in your dependencies?

O3 Security finds GHSA-4c29-gfrp-g6x9 across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works