[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.
Original description
The description as published by the source.
TVT devices utilizing NVMS-1000 software contain a directory traversal vulnerability via GET /.. requests.
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-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.
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.
Path traversal (CWE-22) exists in TVT NVMS-1000. Attackers reach the vulnerable code path via GET /...
Check the vendor advisory for the affected versions of TVT NVMS-1000. Attack surface: GET /...
Severity: High. Risk of unauthorized operations or information disclosure. Listed in CISA KEV — actively exploited in the wild, treat as top priority.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /..' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /..への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Consider incident declaration escalate
Notify SOC / on-callCISA KEV登録済 = 実環境で悪用が観測されている。Step 2 で兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
-
4Post-deployment verification verify
Replay attack against GET /.. on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory NVD