dbcve.org
Industrial Ethernet 1000 Series FirmwareOperating system · Cisco

CVE-2017-6634

HIGH · 8.8 CVSS v3.0 Published 2017-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 the Device Manager web interface of Cisco Industrial Ethernet 1000 Series Switches 1.3 could allow an unauthenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack against a user of an affected system. The vulnerability is due to insufficient CSRF protection by the Device Manager web interface. An attacker could exploit this vulnerability by persuading a user of the interface to follow a malicious link or visit an attacker-controlled website. A successful exploit could allow the attacker to submit arbitrary requests to an affected device via the Device Manager web interface and with the privileges of the user. Cisco Bug IDs: CSCvc88811.

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

A CSRF vulnerability in the Device Manager web interface of Cisco Industrial Ethernet 1000 Series Switches allows unauthenticated remote attackers to trick authenticated users into submitting arbitrary requests. The web interface lacks proper anti-CSRF tokens or validation, enabling attackers to perform actions with the privileges of the victim user.

MitigationApply the vendor patch from Cisco that addresses CSCvc88811. As a workaround, instruct users to avoid clicking untrusted links and to log out of the Device Manager when not in use.

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
Industrial Ethernet 1000 Series FirmwareOperating system
Affected:= 1.3_base

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm device model is Cisco Industrial Ethernet 1000 Series
    Access the device console or web interface and identify the exact model number. For CLI: run 'show version' or 'show hardware' and look for 'Industrial Ethernet 1000' in the product name.
    Affected if The device is not a Cisco Industrial Ethernet 1000 Series Switch - this CVE only applies to that product line.
  2. Check firmware version is 1.3_base
    Via CLI: run 'show version' and examine the firmware/IOS version string. Via web interface: check the Device Manager system information page. Look for a version string exactly matching '1.3_base'.
    Affected if The firmware version is anything other than 1.3_base, or if you cannot determine the version - only version 1.3_base is listed as affected.
  3. Verify Device Manager web interface is enabled
    Via CLI: run 'show ip http server' or 'show running-config | include http' to check if the HTTP/HTTPS web interface is active. Alternatively, attempt to access http://<device-ip> or https://<device-ip> from a browser.
    Affected if The Device Manager web interface is disabled or not accessible - the CSRF vulnerability exists in the web interface code, so it only matters if the interface is running.
  4. Confirm web interface lacks anti-CSRF protection
    Examine login and form submission pages in the Device Manager web interface. Check HTML forms for hidden token fields (look for input type='hidden' with name containing 'csrf', 'token', or 'nonce'). Also check cookies for CSRF-related attributes.
    Affected if No anti-CSRF tokens or SameSite cookie attributes are present in the web interface - this is the core vulnerability condition.

You are affected if you have a Cisco Industrial Ethernet 1000 Series Switch running firmware version 1.3_base with the Device Manager web interface enabled, and the web interface lacks anti-CSRF token validation in its forms.

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

Apply the vendor patch from Cisco that addresses CSCvc88811. As a workaround, instruct users to avoid clicking untrusted links and to log out of the Device Manager when not in use.

Fix this in Industrial Ethernet 1000 Series Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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