Vulnerability in striptags (CVE-2021-32696)
Summary
Vulnerability in striptags (CVE-2021-32696). Risk of unauthorized operations or information disclosure. Exploitable via striptags. Mitigation: upgrade to 3.2.0 or later.
Original description
The description as published by the source.
A type-confusion vulnerability can cause striptags to concatenate unsanitized strings when an array-like object is passed in as the html parameter. This can be abused by an attacker who can control the shape of their input, e.g. if query parameters are passed directly into the function.
Impact
XSS
Patches
3.2.0
Workarounds
Ensure that the html parameter is a string before calling the function.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-2021-32696 has been found in striptags.
Attackers can target a specific entry point like striptags over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade striptags to 3.2.0 or later.
If unsure, ask your IT team or search "striptags CVE-2021-32696" on the vendor's site.
CVE-2021-32696 (striptags) — CWE-241
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: striptags / html
Patched: 3.2.0 — apply immediately
Workaround: Ensure that the html parameter is a string before calling the function.
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.
A vulnerability (CWE-241) exists in striptags. Attackers reach the vulnerable code path via striptags without authentication.
Check the vendor advisory for the affected versions of striptags. Attack surface: striptags / html.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.2.0.
Workaround: Ensure that the html parameter is a string before calling the function.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'striptags' . 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
-
1Identify exposure identify
grep -r 'striptags' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
striptagsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Ensure that the `html` parameter is a string before calling the function.パッチが適用されるまでの応急処置として、Ensure that the
htmlparameter is a string before calling the function. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade striptags to 3.2.0ステージング環境で 3.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web npmjs.com