← Back
CVE-2019-20085
CISA KEV
high
[KEV] Path Traversal in Tvt nvms-1000 (CVE-2019-20085)
Summary
path traversal in Tvt nvms-1000 (CVE-2019-20085). Risk of unauthorized operations or information disclosure. Exploitable via `GET /..`. Listed in CISA KEV — actively exploited.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2019-20085** has been found in Tvt nvms-1000.
Attackers can target a specific entry point like `GET /..` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
Note: CISA has officially confirmed this is **actively exploited in the wild**. Treat it with elevated urgency.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Tvt nvms-1000 CVE-2019-20085" on the vendor's site.
CVE-2019-20085 (Tvt nvms-1000) — CWE-22 /
Attack surface: GET /..
Listed in CISA KEV — actively exploited, treat as top priority.
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
**Path traversal** (CWE-22) exists in Tvt nvms-1000. Attackers reach the vulnerable code path via `GET /..` without authentication.
📍 Affected scope
Tvt nvms-1000 — . Attack surface: GET /...
🔥 Severity
Severity: High. Risk of unauthorized operations or information disclosure **Listed in CISA KEV** — actively exploited in the wild, treat as top priority.
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 `GET /..` requests with malformed payloads or SQL meta-characters. Run `grep -r 'nvms-1000' .` 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 'nvms-1000' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `nvms-1000` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /..' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /..` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
4Consider incident declaration escalate
Notify SOC / on-callCISA KEV登録済 = 実環境で悪用が観測されている。Step 3 で兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
-
7Post-deployment verification verify
Replay attack against GET /.. on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory NVD