Vulnerability in convict (CVE-2022-21190)
Summary
Vulnerability in convict (CVE-2022-21190). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 6.2.3 or later.
Original description
The description as published by the source.
This affects the package convict before 6.2.3. This is a bypass of CVE-2022-22143. The fix introduced, relies on the startsWith method and does not prevent the vulnerability: before splitting the path, it checks if it starts with proto or this.constructor.prototype. To bypass this check it's possible to prepend the dangerous paths with any string value followed by a dot, like for example foo.proto or foo.this.constructor.prototype.
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-2022-21190 has been found in convict.
Successful exploitation can lead to full system takeover.
What to do: upgrade convict to 6.2.3 or later.
If unsure, ask your IT team or search "convict CVE-2022-21190" on the vendor's site.
CVE-2022-21190 (convict) — CWE-1321
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 6.2.3 — 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-1321) exists in convict.
Check the vendor advisory for the affected versions of convict.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 6.2.3.
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 'convict' . 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 'convict' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
convictを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade convict to 6.2.3ステージング環境で 6.2.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory snyk.io
- advisory github.com
- package github.com
- patch github.com
- web gist.github.com
- web github.com
- web github.com