dbcve.org
Web Security ApplianceApplication · Cisco

CVE-2017-6749

MEDIUM · 5.4 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 →
58/100
Remediation priority · Elevated
Remotely reachable

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-based management interface of Cisco Web Security Appliance (WSA) could allow an authenticated, remote attacker to conduct a stored cross-site scripting (XSS) attack against a user of the web-based management interface of an affected device. Affected Products: virtual and hardware versions of Cisco Web Security Appliance (WSA). More Information: CSCvd88865. Known Affected Releases: 10.1.0-204.

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

Stored cross-site scripting (XSS) vulnerability in Cisco Web Security Appliance web-based management interface allows authenticated remote attackers to inject malicious script that persists and executes when other users access the management interface.

MitigationApply the relevant Cisco security patch for CSCvd88865 to affected WSA versions (10.1.0-204 and earlier). If patching is delayed, restrict management interface access to trusted networks and implement Content Security Policy headers.

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-232= 10.0.0-233= 10.0_base= 10.1.0= 10.1.0-204= 10.1.1-230= 10.1.1-234= 10.1.1-235= 10.5.0= 10.5.0-358= 10.5.1-270
Web Security Virtual ApplianceApplication
Affected:= 10.0.0= 10.0_base= 10.1.0= 10.1.1= 10.1_base= 10.5.1= 10.5_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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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. Confirm the device is a Cisco Web Security Appliance
    Access the management interface and check the appliance model name, or run 'version' command in CLI to identify the system as Cisco WSA or WSA Virtual
    Affected if The device is not a Cisco Web Security Appliance or Virtual Appliance (this CVE only applies to WSA products)
  2. Identify the installed firmware version
    In the WSA web interface, go to System Administration > Software Updates > Installed Appliance Version, or use CLI command 'version' to retrieve the exact firmware version number
    Affected if The installed version matches or falls within these ranges: 10.0.0-232, 10.0.0-233, 10.0_base, 10.1.0, 10.1.0-204, 10.1.1-230, 10.1.1-234, 10.1.1-235, 10.5.0, 10.5.0-358, 10.5.1-270 for hardware WSA; or 10.0.0, 10.0_base, 10.1.0, 10.1.1, 10.1_base, 10.5.1, 10.5_base for WSA Virtual
  3. Verify the web-based management interface is enabled
    In WSA CLI, use command 'adminaccessconfig' or check web interface accessibility at https://<WSA-IP>:8080 or https://<WSA-IP> to confirm management interface is active
    Affected if The web-based management interface is enabled and accessible (the XSS vulnerability exists within this interface)
  4. Check network exposure of management interface
    Review network access settings in WSA: go to System Administration > Network Access in the web GUI, or run 'adminaccessconfig > ipaccess' in CLI to list allowed networks for management
    Affected if The management interface is reachable from untrusted networks (this increases exposure to remote attackers who could inject the stored XSS payload)

The environment is affected if the installed Cisco WSA or WSA Virtual version matches one of the affected versions listed AND the web-based management interface is enabled and accessible.

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 relevant Cisco security patch for CSCvd88865 to affected WSA versions (10.1.0-204 and earlier). If patching is delayed, restrict management interface access to trusted networks and implement Content Security Policy headers.

Fix this in Web Security Appliance Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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