← Back
USN-5973-1
Vulnerability in node-url-parse (USN-5973-1)
Summary
vulnerability in node-url-parse (USN-5973-1). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `1.0.5-2ubuntu0.1~esm2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **USN-5973-1** has been found in node-url-parse.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade node-url-parse to **1.0.5-2ubuntu0.1~esm2** or later.
If unsure, ask your IT team or search "node-url-parse USN-5973-1" on the vendor's site.
USN-5973-1 (node-url-parse) —
Patched: `1.0.5-2ubuntu0.1~esm2` — 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.
❓ What is the problem
**A vulnerability** (unclassified) exists in node-url-parse.
📍 Affected scope
node-url-parse — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.0.5-2ubuntu0.1~esm2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'node-url-parse' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'node-url-parse' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `node-url-parse` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade node-url-parse to 1.0.5-2ubuntu0.1~esm2ステージング環境で 1.0.5-2ubuntu0.1~esm2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:Pro:16.04:LTS
node-url-parse
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.5-2ubuntu0.1~esm2"}]}]
Ubuntu:18.04:LTS
node-url-parse
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.0-1ubuntu0.1"}]}]
Ubuntu:20.04:LTS
node-url-parse
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.7-3ubuntu0.1"}]}]
References
- advisory https://ubuntu.com/security/notices/USN-5973-1
- report https://ubuntu.com/security/CVE-2018-3774
- report https://ubuntu.com/security/CVE-2020-8124
- report https://ubuntu.com/security/CVE-2021-3664
- report https://ubuntu.com/security/CVE-2021-27515
- report https://ubuntu.com/security/CVE-2022-0512
- report https://ubuntu.com/security/CVE-2022-0639
- report https://ubuntu.com/security/CVE-2022-0686
- report https://ubuntu.com/security/CVE-2022-0691