Note: articles are for educational purposes and are not professional security advice — consult an expert for your specific needs.

Chrome security update: CVE-2023-5217 zero-day fix

In short

Google Chrome fixed CVE-2023-5217, an actively exploited heap buffer overflow in libvpx VP8 encoding that could allow remote arbitrary code execution. Chrome versions before 117.0.5938.132 are affected; update to 117.0.5938.132 or later.

Summary written with AI from this article, and checked against it.

Google Chrome Update: Patching Critical Zero-Day Vulnerability CVE-2023-5217

Affected systems and impact

FlawAffected systemsImpact
CVE-2023-5217Heap buffer overflow in libvpx VP8 encodingGoogle Chrome before 117.0.5938.132Potential remote arbitrary code execution; actively exploited in spyware attacks
CVE-2023-5186Use after free in password handlingGoogle ChromeNot stated
CVE-2023-5187Use after free in extensionsGoogle ChromeNot stated

At a glanceCVE-2023-5217

CVE-2023-5217 has a CVSS 3.1 base score of 8.8 (High) from NVD. It is fixed in Chrome 117.0.5938.132. Debian bookworm fixed it in chromium 150.0.7871.100-1~deb12u1.

Severity8.8 High (CVSS 3.1, NVD)
Fixed inChrome 117.0.5938.132
AffectedChrome before 117.0.5938.132
ExploitedYes: in CISA's Known Exploited Vulnerabilities catalog since October 2, 2023
EPSS49% chance of exploitation in the next 30 days (FIRST, October 27, 2026)
Public exploitcrbug.com, crbug.com · 3 GitHub repositories name it: proofs of concept, scanners, detections. Unverified: some are fake or malicious.
VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
WeaknessCWE-787 Out-of-bounds Write
UbuntuNot tracked yet
Debianbookworm chromium: Fixed (150.0.7871.100-1~deb12u1) · trixie chromium: Fixed (150.0.7871.181-1~deb13u1) · forky, sid chromium: Fixed (156.0.8078.47-1) · sid firefox: Vulnerable · bookworm firefox-esr: Vulnerable · trixie firefox-esr: Vulnerable
Red HatFixed: RHEL 7 (RHSA-2023:5475, RHSA-2023:5477), RHEL 8 (RHSA-2023:5428, RHSA-2023:5433, RHSA-2023:5537), RHEL 8.1 Update Services for SAP Solutions (RHSA-2023:5438, RHSA-2023:5440, RHSA-2023:5535) · RHEL 6: Out of support scope, RHEL 9: Affected, RHEL 9: Affected
Also inWebmproject libvpx, Microsoft edge, Microsoft edge chromium, Firefox, Mozilla thunderbird, Fedoraproject fedora

Is there a public exploit for CVE-2023-5217?

Yes: CVE-2023-5217 is exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on October 2, 2023. NVD links 2 exploit references and 3 public GitHub repositories name it: proofs of concept, scanners and detections. None of it is verified: some such repositories are fake or carry malware, so read the code before running it, and only against systems you own. FIRST's EPSS puts the chance of exploitation in the next 30 days at 49%, higher than 98.8% of scored CVEs.

From NVD, Debian, Red Hat · checked October 28, 2026

Google has recently patched a series of vulnerabilities in Google Chrome, including a high-severity zero-day vulnerability, CVE-2023-5217. This particular vulnerability, stemming from a heap buffer overflow in the VP8 encoding of the libvpx video codec library, has been actively exploited in spyware attacks, underlining its criticality.

Detailed Analysis of the Vulnerabilities

The vulnerabilities uncovered in Google Chrome include:

  1. CVE-2023-5217 (Heap-Based Buffer Overflow): This vulnerability is critical due to its potential to allow malicious actors to execute arbitrary code remotely. It was discovered within the VP8 encoding component of the open-source libvpx video codec library. Clément Lecigne from Google's Threat Analysis Group (TAG) first reported it.
  2. CVE-2023-5186 (Use After Free in Password Handling): This vulnerability has a high risk score of 9.8 and is related to password handling within Chrome.
  3. CVE-2023-5187 (Use After Free in Extensions): Also scoring 9.8, this vulnerability involves a Use-After-Free scenario associated with Chrome Extensions.

The exploitation of CVE-2023-5217 has been observed in the deployment of spyware, targeting high-risk individuals such as journalists and political opposition figures. This underscores the vulnerability's severity and the need for immediate action.

Recommendations for Users and System Administrators

  1. Apply Updates Immediately: Users should promptly apply the latest updates provided by Google, particularly Chrome version 117.0.5938.132, to all vulnerable systems.
  2. Establish a Vulnerability Management Process: It is essential for enterprises to create and maintain a documented vulnerability management process. This process should be reviewed and updated annually or with significant enterprise changes.
  3. Implement Automated Application Patch Management: Automated patch management for application updates on enterprise assets is crucial. Conducting these updates on a monthly or more frequent basis is recommended to ensure timely protection against potential exploits.

Conclusion

The identification of multiple vulnerabilities in Google Chrome, including a critical zero-day flaw, highlights the ongoing challenges in cybersecurity. Immediate application of the provided updates is imperative to protect against arbitrary code execution and potential compromise of user data and system integrity. Establishing robust vulnerability management processes is equally important in mitigating these risks.

In the face of these significant vulnerabilities, including the zero-day threat in Google Chrome, users and organizations must be vigilant. Proactive measures such as timely updates and a robust vulnerability management strategy are essential in safeguarding against potential cyber threats and maintaining system integrity.

Quick revision

Interview flashcards

  1. What causes CVE-2023-5217 in Chrome, and what could it allow an attacker to do?

    CVE-2023-5217 is a heap buffer overflow in the VP8 encoding component of the open-source libvpx video codec library. It could allow malicious actors to execute arbitrary code remotely.

  2. How has CVE-2023-5217 been exploited?

    CVE-2023-5217 has been actively exploited in spyware attacks targeting high-risk individuals, including journalists and political opposition figures.

  3. Which Chrome version should be applied to address these vulnerabilities?

    Chrome version 117.0.5938.132 should be applied promptly to all vulnerable systems. Immediate updating helps protect against arbitrary code execution and potential compromise of user data and system integrity.

  4. What is CVE-2023-5186?

    CVE-2023-5186 is a use-after-free vulnerability related to password handling in Chrome. It has a high risk score of 9.8.

  5. What is CVE-2023-5187?

    CVE-2023-5187 is a use-after-free vulnerability associated with Chrome Extensions. It has a high risk score of 9.8.

  6. How often should an enterprise review its documented vulnerability management process?

    An enterprise should review and update its documented vulnerability management process annually or when significant enterprise changes occur.

  7. How frequently should enterprises apply automated application updates?

    Enterprises should use automated application patch management on enterprise assets monthly or more frequently to ensure timely protection against potential exploits.

Written with AI from this article, and checked against it.

Source

  1. CVE recordCVE-2023-5217 in the National Vulnerability Database · nvd.nist.gov
Vishal

About the author

· Software & security engineer

GitHub · LinkedIn · X

Vishal writes Trickyworld's tutorials and interview-preparation guides on programming, databases, cyber security and AI. Vishal has been shipping production software long enough to have firm opinions about Python, PHP, Node.js, and JavaScript, and to have been wrong about each of them at least once. The work has run the whole stack: Drupal and Laravel applications, React front ends, MySQL and MongoDB underneath, Redis and Memcached for the things that had to be fast, Apache Solr for the things that had to be findable. That last part turned out to matter more than anyone expected. Tune a Solr index for a season, then watch a language model confidently retrieve the wrong document, and you recognise an old problem wearing new clothes. Most of what is hard about AI systems is not the model. It is retrieval, caching, latency budgets, and deciding what the system does when the answer comes back wrong — which is work he has been doing since well before anyone called it AI engineering. He plays a lot of games, which is less a hobby disclosure than an admission of where a good share of his engineering instinct came from. Real-time systems with a frame budget. State that has to stay coherent while a player does something no designer anticipated. The permanent question of what happens when the frame cannot finish in time. Those habits carry over more directly than they have any right to. He has written several books on programming, all built on the same conviction: most technical writing is unclear because the author never decided what to leave out. More from Vishal → · Editorial policy

#heap buffer overflow#libvpx video codec#Zero-Day Vulnerability#Google Chrome#code execution#spyware attacks#CVE-2023-5217

More on Computer Tricks.

Latest articles

$ subscribe --weekly

Get the next tutorial in your inbox.

Programming, security and AI — the practical bits, no spam. Unsubscribe any time.