dbcve.org
Ios XrOperating system · Cisco

CVE-2016-1366

MEDIUM · 6.5 CVSS v3.0 Published 2016-03-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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
The SCP and SFTP modules in Cisco IOS XR 5.0.0 through 5.2.5 on Network Convergence System 6000 devices use weak permissions for system files, which allows remote authenticated users to cause a denial of service (overwrite) via unspecified vectors, aka Bug ID CSCuw75848.

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 SCP and SFTP modules in Cisco IOS XR versions 5.0.0 through 5.2.5 on Network Convergence System 6000 devices contain weak file permissions on system files. This allows any remote authenticated user to overwrite system files, causing a denial of service condition.

MitigationUpgrade Cisco IOS XR to a version beyond 5.2.5 that addresses this vulnerability. If immediate patching is not feasible, restrict SCP/SFTP access to only highly trusted administrative accounts and monitor for unauthorized access attempts.

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
Ios XrOperating system
Affected:= 5.0.0= 5.0.1= 5.2.1= 5.2.3= 5.2.4= 5.2.5

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
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 IOS XR version on the NCS 6000 device
    Execute 'show version' or 'admin show version' in the IOS XR CLI to obtain the running software version
    Affected if The displayed version falls within 5.0.0 through 5.2.5 (including 5.0.0, 5.0.1, 5.2.1, 5.2.3, 5.2.4, 5.2.5)
  2. Verify SCP module is enabled
    Check the configuration with 'show running-config | include scp' or review the SCP service status in the IOS XR configuration
    Affected if SCP is configured and active on the device
  3. Verify SFTP module is enabled
    Check the configuration with 'show running-config | include sftp' or review the SFTP service status in the IOS XR configuration
    Affected if SFTP is configured and active on the device
  4. Confirm the device is a NCS 6000 platform
    Execute 'show inventory' or 'admin show inventory' to identify the hardware platform
    Affected if The device is a Network Convergence System 6000 (NCS 6000) series platform

The device is affected if it is an NCS 6000 running Cisco IOS XR version 5.0.0 through 5.2.5 with either SCP or SFTP module enabled and accessible to authenticated users.

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

Upgrade Cisco IOS XR to a version beyond 5.2.5 that addresses this vulnerability. If immediate patching is not feasible, restrict SCP/SFTP access to only highly trusted administrative accounts and monitor for unauthorized access attempts.

Fix this in Ios Xr Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1366 — 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-2016-1366 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