Vulnerability in detect-character-encoding (CVE-2021-39176)
Summary
Vulnerability in detect-character-encoding (CVE-2021-39176). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.3.1 or later.
Original description
The description as published by the source.
detect-character-encoding is a package for detecting character encoding using ICU. In detect-character-encoding v0.3.0 and earlier, allocated memory is not released. The problem has been patched in detect-character-encoding v0.3.1.
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-39176 has been found in detect-character-encoding.
Risk of unauthorized operations or information disclosure.
What to do: upgrade detect-character-encoding to 0.3.1 or later.
If unsure, ask your IT team or search "detect-character-encoding CVE-2021-39176" on the vendor's site.
CVE-2021-39176 (detect-character-encoding) — CWE-401
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.3.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.
A vulnerability (CWE-401) exists in detect-character-encoding.
Check the vendor advisory for the affected versions of detect-character-encoding.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.3.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'detect-character-encoding' . 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 'detect-character-encoding' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
detect-character-encodingを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade detect-character-encoding to 0.3.1ステージング環境で 0.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch github.com