Vulnerability in html-sanitizer (CVE-2024-34078)

Summary

vulnerability in html-sanitizer (CVE-2024-34078). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.4.2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2024-34078** has been found in html-sanitizer. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade html-sanitizer to **2.4.2** or later. If unsure, ask your IT team or search "html-sanitizer CVE-2024-34078" on the vendor's site.

CVE-2024-34078 (html-sanitizer) — Patched: `2.4.2` — apply immediately Workaround: Set `keep_typographic_whitespace=True` explicitly, or normalize to NFKC yourself earlier. 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

**A vulnerability** (unclassified) exists in html-sanitizer.

📍 Affected scope

html-sanitizer — .

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **2.4.2**.

🛡️ Workaround

Workaround: Set `keep_typographic_whitespace=True` explicitly, or normalize to NFKC yourself earlier.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'html-sanitizer' .` 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 'html-sanitizer' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `html-sanitizer` を grep し、稼働しているサービス・バージョンを把握する。
5
Apply temporary workaround mitigate
```
Set `keep_typographic_whitespace=True` explicitly, or normalize to NFKC yourself earlier.
```
パッチが適用されるまでの応急処置として、Set `keep_typographic_whitespace=True` explicitly, or normalize to NFKC yourself earlier. を実施。回避策の副作用 (機能低下) を確認した上で。
6
Apply patch patch
```
Upgrade html-sanitizer to 2.4.2
```
ステージング環境で 2.4.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI html-sanitizer

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