Vulnerability in Cisco Asr 5000 Software (CVE-2017-6690)
Summary
Vulnerability in Cisco Asr 5000 Software (CVE-2017-6690). Data can be tampered with by attackers.
Original description
The description as published by the source.
A vulnerability in the file check operation of Cisco ASR 5000 Series Aggregated Services Routers running the Cisco StarOS operating system could allow an authenticated, remote attacker to overwrite or modify arbitrary files on an affected system. More Information: CSCvd73726. Known Affected Releases: 21.0.v0.65839 21.3.M0.67005. Known Fixed Releases: 21.4.A0.67087 21.4.A0.67079 21.4.A0.67013 21.3.M0.67084 21.3.M0.67077 21.3.M0.66994 21.3.J0.66993 21.1.v0.67082 21.1.V0.67083.
Source: NIST National Vulnerability Database NVD
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-2017-6690 has been found in Cisco Asr 5000 Software.
Data can be tampered with by attackers. CVSS score: 4.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Cisco Asr 5000 Software CVE-2017-6690" on the vendor's site.
CVE-2017-6690 (Cisco Asr 5000 Software) — CWE-20 / CVSS v3 4.9
Attack vector: remote (network-reachable) / no user interaction
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-20) exists in Cisco Asr 5000 Software.
Check the vendor advisory for the affected versions of Cisco Asr 5000 Software.
Severity: Medium (CVSS 4.9/10). Data can be tampered with by attackers.
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 request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Cisco Asr 5000 Software を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory securityfocus.com
- patch tools.cisco.com
- web securitytracker.com