dbcve.org
Asr 5000 SoftwareApplication · Cisco

CVE-2017-6774

MEDIUM · 5.0 CVSS v3.0 Published 2017-08-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability in Cisco ASR 5000 Series Aggregated Services Routers running the Cisco StarOS operating system could allow an authenticated, remote attacker to overwrite or modify sensitive system files. The vulnerability is due to the inclusion of sensitive system files within specific FTP subdirectories. An attacker could exploit this vulnerability by overwriting sensitive configuration files through FTP. An exploit could allow the attacker to overwrite configuration files on an affected system. Cisco Bug IDs: CSCvd47739. Known Affected Releases: 21.0.v0.65839.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Cisco ASR 5000 Series Aggregated Services Router running StarOS contains sensitive system configuration files within FTP-accessible subdirectories. An authenticated remote attacker with FTP access can overwrite these sensitive configuration files, potentially modifying system behavior or gaining additional access.

MitigationRestrict or disable FTP access to sensitive directories, implement proper file permissions, or relocate sensitive configuration files outside FTP-accessible paths. Consider using SFTP/FTPS with stricter access controls as an alternative.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Asr 5000 SoftwareApplication
Affected:= 21.0.v0.65839

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the system platform and software version
    Run 'show version' or access the StarOS CLI to confirm the device is a Cisco ASR 5000 Series and obtain the exact StarOS version number
    Affected if The installed version is 21.0.v0.65839 exactly (note: only this specific version is affected)
  2. Verify FTP service is enabled
    Check the StarOS configuration for FTP server settings using 'show configuration' or 'show ftp' commands, or examine the running configuration for ftp-server related entries
    Affected if FTP is enabled and configured on the system - the vulnerability requires FTP access to be present
  3. Confirm FTP-accessible directories exist
    Review the FTP root directory structure and identify which subdirectories are accessible via FTP; check file permissions on configuration directories
    Affected if Sensitive system configuration files reside within FTP-accessible subdirectories (the flaw is that these should not be FTP-accessible)
  4. Review FTP user permissions
    Examine FTP user accounts and their assigned directories using 'show ftp users' or equivalent to determine if authenticated users can write to configuration directories
    Affected if Authenticated FTP users have write permissions to directories containing sensitive configuration files

A system is affected if it is a Cisco ASR 5000 running StarOS version 21.0.v0.65839 with FTP enabled and sensitive configuration files accessible via authenticated FTP write access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict or disable FTP access to sensitive directories, implement proper file permissions, or relocate sensitive configuration files outside FTP-accessible paths. Consider using SFTP/FTPS with stricter access controls as an alternative.

Fix this in Asr 5000 Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-6774 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-6774 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data