dbcve.org
Web Security ApplianceApplication · Cisco

CVE-2017-6751

HIGH · 7.5 CVSS v3.1 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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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 proxy functionality of the Cisco Web Security Appliance (WSA) could allow an unauthenticated, remote attacker to forward traffic from the web proxy interface of an affected device to the administrative management interface of an affected device, aka an Access Control Bypass Vulnerability. Affected Products: virtual and hardware versions of Cisco Web Security Appliance (WSA). More Information: CSCvd88863. Known Affected Releases: 10.1.0-204 9.0.0-485.

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 vulnerability allows an unauthenticated remote attacker to forward traffic from the Cisco WSA web proxy interface to the administrative management interface of the same device, bypassing access controls. This enables potential attackers to reach internal management interfaces through the proxy, which should normally be restricted.

MitigationApply Cisco security updates for WSA (refer to CSCvd88863) and implement network segmentation to isolate the administrative management interface from the web proxy interface.

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:= 9.0.0-162= 9.0.0-193= 9.0.0-485= 10.0.0-232= 10.0.0-233= 10.1.0-204
Web Security Virtual ApplianceApplication
Affected:= 9.0.0= 10.0.0= 10.1.0= 10.1.1

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

CVSS:3.1/AV:N/AC:L/PR:N/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 device model and software version
    Log into the Cisco WSA CLI and run the 'version' command or 'show version' to display the installed software version and appliance model.
    Affected if The device is a Cisco Web Security Appliance (WSA) or WSA Virtual Appliance and the displayed version matches one of the following: 9.0.0-162, 9.0.0-193, 9.0.0-485, 10.0.0-232, 10.0.0-233, 10.1.0-204 (for hardware WSA) or 9.0.0, 10.0.0, 10.1.0, 10.1.1 (for WSA Virtual).
  2. Confirm the web proxy service is enabled
    In the WSA CLI, run 'proxyconfig' or check the web UI under Security Services > Proxy to verify that the HTTPS proxy or HTTP proxy service is currently enabled.
    Affected if The proxy service is enabled and the version matches the affected list in step 1.
  3. Verify network accessibility of the proxy interface
    Check the interface configuration using 'interfaceconfig' in the CLI or via the web UI under Network > Interfaces. Determine if the proxy listener is bound to an externally accessible IP address or interface.
    Affected if The proxy interface is bound to a routable or externally accessible IP address and the version is affected.
  4. Check for internal management interface exposure via proxy
    Attempt to access the internal management interface (typically port 8443 or port 8080 for admin) through the proxy service from an untrusted network. This can be tested by configuring a client to use the WSA as a proxy and attempting to connect to the device's own management IP or localhost through that proxy.
    Affected if Traffic from the proxy interface can reach the administrative management interface of the same device, indicating the vulnerability is exploitable.

A user is affected if they are running a Cisco WSA or WSA Virtual Appliance with a version matching the affected ranges and the web proxy service is enabled with network accessibility.

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 Cisco security updates for WSA (refer to CSCvd88863) and implement network segmentation to isolate the administrative management interface from the web proxy interface.

Fix this in Web Security Appliance Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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