Vulnerability in i18n (CVE-2020-7791)
Summary
Vulnerability in i18n (CVE-2020-7791). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.1.15 or later.
Original description
The description as published by the source.
This affects the package i18n before version 2.1.15. Vulnerability arises out of insufficient handling of erroneous language tags in src/i18n/Concrete/TextLocalizer.cs and src/i18n/LocalizedApplication.cs.
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-2020-7791 has been found in i18n.
Risk of unauthorized operations or information disclosure.
What to do: upgrade i18n to 2.1.15 or later.
If unsure, ask your IT team or search "i18n CVE-2020-7791" on the vendor's site.
CVE-2020-7791 (i18n) — CWE-20
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.1.15 — 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-20) exists in i18n.
Check the vendor advisory for the affected versions of i18n.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.1.15.
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 'i18n' . 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 'i18n' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
i18nを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade i18n to 2.1.15ステージング環境で 2.1.15 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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 lists.apache.org
- web lists.apache.org
- web lists.apache.org
- web lists.apache.org
- web lists.apache.org
- web lists.apache.org
- web lists.apache.org
- web lists.apache.org
- web lists.apache.org
- web snyk.io