Web Security ApplianceApplication · Cisco

CVE-2017-6746

HIGH · 7.2 CVSS v3.0 Published 2017-07-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 the web interface of the Cisco Web Security Appliance (WSA) could allow an authenticated, remote attacker to perform command injection and elevate privileges to root. The attacker must authenticate with valid administrator credentials. Affected Products: Cisco AsyncOS Software 10.0 and later for WSA on both virtual and hardware appliances. More Information: CSCvd88862. Known Affected Releases: 10.1.0-204. Known Fixed Releases: 10.5.1-270 10.1.1-235.

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 command injection vulnerability in the Cisco Web Security Appliance web interface allows an authenticated remote attacker with administrator credentials to execute arbitrary commands with root privileges. The vulnerability exists in AsyncOS Software version 10.0 and later.

MitigationUpgrade Cisco AsyncOS Software to fixed release 10.5.1-270 or 10.1.1-235. Restrict administrative access to trusted networks and enforce strong credential policies.

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
Web Security ApplianceApplication
Affected:= 10.0.0-233= 10.0_base= 10.1.0= 10.1.0-204= 10.1.1-230= 10.1.1-234= 10.5.0= 10.5.0-358= 11.0.0= 11.0.0-613= 11.0.0-641

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

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/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. Determine the AsyncOS version
    Access the appliance CLI and run the 'version' command, or log into the web interface and check System Administration > AsyncOS Software version
    Affected if The displayed version matches any of: 10.0.0-233, 10.0_base, 10.1.0, 10.1.0-204, 10.1.1-230, 10.1.1-234, 10.5.0, 10.5.0-358, 11.0.0, 11.0.0-613, or 11.0.0-641 (or falls within the 10.0.x to 11.0.x range without having applied the fixed releases)
  2. Confirm the web interface is enabled
    In the CLI, run 'interfaceconfig' or check through the web interface under Network > IP Interfaces to verify the HTTP/HTTPS management interface is active
    Affected if The web interface (HTTP or HTTPS) is enabled and accessible on any management interface
  3. Verify administrator account exposure
    Check the appliance's administrative access settings: in the CLI run 'ipaccess' or through the web interface under System Administration > Administrative Users > Access Settings
    Affected if Administrative access is permitted from untrusted networks or the web interface is exposed to the internet or wide-area networks

You are affected if your Cisco Web Security Appliance runs any AsyncOS version between 10.0 and 11.0.0-641, has the web interface enabled, and administrative access is possible from your network.

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 AsyncOS Software to fixed release 10.5.1-270 or 10.1.1-235. Restrict administrative access to trusted networks and enforce strong credential policies.

Fix this in Web Security Appliance Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-6746 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