Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2023-5217 CISA KEV high

[KEV] Out-of-Bounds Write in Google Chromium libvpx (CVE-2023-5217)

Summary

Out-of-bounds write in Google Chromium libvpx (CVE-2023-5217). Successful exploitation can lead to full system takeover. Listed in CISA KEV — actively exploited. Mitigation: upgrade to 27.0.0-beta.8 or later.

Original description

The description as published by the source.

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.

Source: CISA Known Exploited Vulnerabilities NVD GitHub Advisory CISA KEV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2023-5217 has been found in Google Chromium libvpx.
Successful exploitation can lead to full system takeover.
Note: CISA has officially confirmed this is actively exploited in the wild. Treat it with elevated urgency.
What to do: upgrade Google Chromium libvpx to 27.0.0-beta.8 or later.
If unsure, ask your IT team or search "Google Chromium libvpx CVE-2023-5217" on the vendor's site.

CVE-2023-5217 (Google Chromium libvpx) — CWE-787
Attack vector: remote (network-reachable) / unauthenticated
Patched: 27.0.0-beta.8 — apply immediately
Listed in CISA KEV — actively exploited, treat as top priority.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Out-of-bounds write (CWE-787) exists in Google Chromium libvpx.

📍 Affected scope

Check the vendor advisory for the affected versions of Google Chromium libvpx.

🔥 Severity

Severity: High. Successful exploitation can lead to full system takeover. Listed in CISA KEV — actively exploited in the wild, treat as top priority.

🔧 How to fix

Update to 27.0.0-beta.8.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'electron' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'electron' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で electron を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Consider incident declaration escalate 
    Notify SOC / on-call

    CISA KEV登録済 = 実環境で悪用が観測されている。侵入の兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。

  3. 3
    Apply patch patch 
    Upgrade Google Chromium libvpx to 27.0.0-beta.8

    ステージング環境で 27.0.0-beta.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm electron
[{"type":"SEMVER","events":[{"introduced":"27.0.0-alpha.1"},{"fixed":"27.0.0-beta.8"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details