GHSA-4c29-gfrp-g6x9 json
CefSharp affected by libvpx's heap buffer overflow in vp8 encoding
published 3y ago modified last yr.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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
Patch / fix
- nuget CefSharp.Common 117.2.20
- nuget CefSharp.Common.NETCore 117.2.20
Is GHSA-4c29-gfrp-g6x9 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| nuget | CefSharp.Common | <117.2.20 |
117.2.20 |
| nuget | CefSharp.Common.NETCore | <117.2.20 |
117.2.20 |
References
Sources
- GitHub Advisory GHSA-4c29-gfrp-g6x9
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.