dbcve.org
Anyconnect Secure Mobility ClientApplication · Cisco

CVE-2017-6788

MEDIUM · 6.1 CVSS v3.0 Published 2017-08-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
The WebLaunch functionality of Cisco AnyConnect Secure Mobility Client Software contains a vulnerability that could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the affected software. The vulnerability is due to insufficient input validation of some parameters that are passed to the WebLaunch function of the affected software. An attacker could exploit this vulnerability by convincing a user to access a malicious link or by intercepting a user request and injecting malicious code into the request. Cisco Bug IDs: CSCvf12055. Known Affected Releases: 98.89(40).

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

Cross-site scripting (XSS) vulnerability in the WebLaunch functionality of Cisco AnyConnect Secure Mobility Client Software. The WebLaunch function insufficiently validates input parameters, allowing unauthenticated remote attackers to inject malicious script through crafted URLs or by intercepting and modifying user requests.

MitigationApply vendor patches from Cisco for affected AnyConnect versions. Until patched, users should avoid clicking untrusted links. Network-level URL filtering may provide additional protection but does not remediate the underlying vulnerability.

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
Anyconnect Secure Mobility ClientApplication
Affected:= 4.4\(4027\)= 4.5\(58\)

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/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. Identify installed Cisco AnyConnect version on Windows
    Open Control Panel > Programs and Features, locate 'Cisco AnyConnect Secure Mobility Client', and note the version column. Alternatively, open Command Prompt and run: wmic product get name,version
    Affected if The displayed version matches exactly 4.4.4027 or 4.5.58
  2. Identify installed Cisco AnyConnect version on macOS
    Open Finder, go to /Applications, right-click Cisco AnyConnect.app, select Get Info, and check the version under Version:
    Affected if The displayed version matches exactly 4.4.4027 or 4.5.58
  3. Check AnyConnect executable version directly
    Navigate to the AnyConnect installation directory (typically C:\Program Files\Cisco\Cisco AnyConnect Secure Mobility Client\ on Windows or /Applications/Cisco/AnyConnect on macOS), right-click vpnui.exe or the AnyConnect application, select Properties, and view the File Version information
    Affected if The file version shows 4.4.4027 or 4.5.58
  4. Confirm WebLaunch module is present
    Check if the WebLaunch feature is available in the AnyConnect client interface. Look for web-based launch options or portal integration features within the client
    Affected if WebLaunch functionality is present and accessible in the client

A user is affected if their installed Cisco AnyConnect Secure Mobility Client version is exactly 4.4.4027 or 4.5.58 and they have access to the WebLaunch feature.

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 vendor patches from Cisco for affected AnyConnect versions. Until patched, users should avoid clicking untrusted links. Network-level URL filtering may provide additional protection but does not remediate the underlying vulnerability.

Fix this in Anyconnect Secure Mobility Client Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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