CVE-2023-4863 CISA KEV high

[KEV] Out-of-Bounds Write in Google Chromium WebP (CVE-2023-4863)

Summary

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

Original description

The description as published by the source.

In BuildHuffmanTable of huffman_utils.c, there is a possible out of bounds write due to a heap buffer overflow. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

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-4863 has been found in Google Chromium WebP.
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 WebP to 0.1.8 or later.
If unsure, ask your IT team or search "Google Chromium WebP CVE-2023-4863" on the vendor's site.

CVE-2023-4863 (Google Chromium WebP) — CWE-787
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.1.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 WebP.

📍 Affected scope

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

🔥 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 0.1.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 'libwebp-sys2' . 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
Identify exposure identify
```
grep -r 'libwebp-sys2' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で libwebp-sys2 を grep し、稼働しているサービス・バージョンを把握する。
2
Consider incident declaration escalate
```
Notify SOC / on-call
```
CISA KEV登録済 = 実環境で悪用が観測されている。侵入の兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
3
Apply patch patch
```
Upgrade Google Chromium WebP to 0.1.8
```
ステージング環境で 0.1.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
4
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

crates.io libwebp-sys2

[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"0.1.8"}]}]

crates.io libwebp-sys

[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"0.9.3"}]}]

npm electron

[{"type":"SEMVER","events":[{"introduced":"27.0.0-beta.1"},{"fixed":"27.0.0-beta.2"}]}]

NuGet SkiaSharp

[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0"},{"fixed":"2.88.6"}]}]

Go github.com/chai2010/webp

[{"type":"SEMVER","events":[{"introduced":"0.0.0"},{"fixed":"1.1.2-0.20250406010349-76805d5a8860"}]}]

PyPI pillow

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.0.1"}]}]

crates.io webp

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.2.6"}]}]

NuGet magick.net-q16-anycpu