Vulnerability in chrono-node (CVE-2021-23371)
Summary
Vulnerability in chrono-node (CVE-2021-23371). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.2.4 or later.
Original description
The description as published by the source.
This affects the package chrono-node before 2.2.4. It hangs on a date-like string with lots of embedded spaces.
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-23371 has been found in chrono-node.
Risk of unauthorized operations or information disclosure.
What to do: upgrade chrono-node to 2.2.4 or later.
If unsure, ask your IT team or search "chrono-node CVE-2021-23371" on the vendor's site.
CVE-2021-23371 (chrono-node) — CWE-400
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.2.4 — 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-400) exists in chrono-node.
Check the vendor advisory for the affected versions of chrono-node.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.2.4.
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 'chrono-node' . 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 'chrono-node' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
chrono-nodeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade chrono-node to 2.2.4ステージング環境で 2.2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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 snyk.io