← Back
GHSA-gj48-438w-jh9v
Cross-Site Scripting (XSS) in bleach (GHSA-gj48-438w-jh9v)
Summary
cross-site scripting in bleach (GHSA-gj48-438w-jh9v). Risk of unauthorized operations or information disclosure. Exploitable via ``formaction``. Mitigation: upgrade to `6.4.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-gj48-438w-jh9v** has been found in bleach.
Attackers can target a specific entry point like ``formaction`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade bleach to **6.4.0** or later.
If unsure, ask your IT team or search "bleach GHSA-gj48-438w-jh9v" on the vendor's site.
GHSA-gj48-438w-jh9v (bleach) — CWE-79 /
Attack surface: `formaction` / `attr_val_is_uri` / `action` / `href`
Patched: `6.4.0` — 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
**Cross-site scripting (XSS)** (CWE-79) exists in bleach. Attackers reach the vulnerable code path via ``formaction`` without authentication.
📍 Affected scope
bleach — . Attack surface: `formaction` / `attr_val_is_uri` / `action` / `href`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **6.4.0**.
🛡️ 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 'bleach' .` 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 'bleach' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `bleach` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade bleach to 6.4.0ステージング環境で 6.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
bleach
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0"}]}]