← Back
CVE-2024-21501
Information Disclosure in sanitize-html (CVE-2024-21501)
Summary
vulnerability in sanitize-html (CVE-2024-21501). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.12.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-21501** has been found in sanitize-html.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade sanitize-html to **2.12.1** or later.
If unsure, ask your IT team or search "sanitize-html CVE-2024-21501" on the vendor's site.
CVE-2024-21501 (sanitize-html) — CWE-200 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `2.12.1` — apply immediately
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
**information disclosure** (CWE-200) exists in sanitize-html.
📍 Affected scope
sanitize-html — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.12.1**.
🛡️ 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 'sanitize-html' .` 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
-
1Identify exposure identify
grep -r 'sanitize-html' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `sanitize-html` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade sanitize-html to 2.12.1ステージング環境で 2.12.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
sanitize-html
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.12.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-21501
- package https://github.com/apostrophecms/sanitize-html
- web https://github.com/apostrophecms/sanitize-html/pull/650
- web https://github.com/apostrophecms/sanitize-html/commit/c5dbdf77fe8b836d3bf4554ea39edb45281ec0b4
- web https://gist.github.com/Slonser/8b4d061abe6ee1b2e10c7242987674cf
- web https://github.com/apostrophecms/apostrophe/discussions/4436
- web https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4EB5JPYRCTS64EA5AMV3INHDPI6I4AW7
- web https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/P4I5X6V3LYUNBMZ5YOW4BV427TH3IK4S
- web https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-6276557
- web https://security.snyk.io/vuln/SNYK-JS-SANITIZEHTML-6256334