[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.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2023-4863** has been found in Google chromium-webp. Successful exploitation can lead to full system takeover. CVSS score: ?/10. Note: CISA has officially confirmed this is **actively exploited in the wild**. Treat it with elevated urgency. What to do: apply the vendor's official patched release. 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 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

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 the patched release per vendor advisory.

🛡️ 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 'chromium-webp' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

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

1
Identify exposure identify
```
grep -r 'chromium-webp' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `chromium-webp` を grep し、稼働しているサービス・バージョンを把握する。
4
Consider incident declaration escalate
```
Notify SOC / on-call
```
CISA KEV登録済 = 実環境で悪用が観測されている。Step 3 で兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

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