Vulnerability in date-and-time (CVE-2020-26289)
Summary
Vulnerability in date-and-time (CVE-2020-26289). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.14.2 or later.
Original description
The description as published by the source.
date-and-time is an npm package for manipulating date and time. In date-and-time before version 0.14.2, there a regular expression involved in parsing which can be exploited to to cause a denial of service. This is fixed in version 0.14.2.
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-26289 has been found in date-and-time.
Risk of unauthorized operations or information disclosure.
What to do: upgrade date-and-time to 0.14.2 or later.
If unsure, ask your IT team or search "date-and-time CVE-2020-26289" on the vendor's site.
CVE-2020-26289 (date-and-time) — CWE-400
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.14.2 — 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 date-and-time.
Check the vendor advisory for the affected versions of date-and-time.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.14.2.
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 'date-and-time' . 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 'date-and-time' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
date-and-timeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade date-and-time to 0.14.2ステージング環境で 0.14.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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 npmjs.com
- web npmjs.com