dbcve.org
Anyconnect Secure Mobility ClientApplication · Cisco

CVE-2015-6322

MEDIUM · 6.6 CVSS v2.0 Published 2015-10-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
The IPC channel in Cisco AnyConnect Secure Mobility Client 2.0.0343 through 4.1(8) allows local users to bypass intended access restrictions and move arbitrary files by leveraging the lack of source-path validation, aka Bug ID CSCuv48563.

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 IPC channel in Cisco AnyConnect Secure Mobility Client versions 2.0.0343 through 4.1(8) lacks source-path validation, allowing local users to bypass intended access restrictions and move arbitrary files to arbitrary locations on the system.

MitigationApply the vendor-supplied patch or upgrade to a version beyond 4.1(8) that addresses the source-path validation flaw in the IPC channel. As a workaround, restrict local user access to the AnyConnect installation directories and monitor for suspicious file operations.

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:= 2.0.0343= 2.1.0148= 2.2.0133= 2.2.0136= 2.2.0140= 2.3.0185= 2.3.0254= 2.3.1003= 2.3.2016= 2.4.0202= 2.4.1012= 2.5.0217

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
Local
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:N/C:N/I:C/A:C

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. Verify Cisco AnyConnect installation
    Search for the AnyConnect client executable (e.g., vpnui.exe, acagent.exe, or anyconnect.exe) in common installation paths such as C:\Program Files\Cisco\Cisco AnyConnect Secure Mobility Client\ or C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\, or check Add/Remove Programs for Cisco AnyConnect.
    Affected if The software is not found, meaning the product is not installed and the system is not affected.
  2. Identify installed AnyConnect version
    Right-click the AnyConnect executable (e.g., vpnui.exe), select Properties, and check the Details tab for the File Version. Alternatively, open Windows Control Panel > Programs and Features, locate Cisco AnyConnect Secure Mobility Client, and note the version shown.
    Affected if The installed version matches any of these: 2.0.0343, 2.1.0148, 2.2.0133, 2.2.0136, 2.2.0140, 2.3.0185, 2.3.0254, 2.3.1003, 2.3.2016, 2.4.0202, 2.4.1012, 2.5.0217, or any version through 4.1(8). Compare your version against this list and the upper bound.
  3. Check if AnyConnect IPC service is accessible to local users
    Examine the file permissions on the AnyConnect installation directory and its subdirectories. Right-click the Cisco AnyConnect folder, select Properties > Security tab, and review which users and groups have Read, Write, or Modify permissions. Also check if the AnyConnect agent service (often named 'Cisco AnyConnect Agent' or 'acagent') allows interaction with non-privileged local users.
    Affected if Non-administrative local user accounts have write or modify access to the AnyConnect installation directory or can interact with the IPC channel, indicating the vulnerable feature is exposed.
  4. Inspect IPC channel configuration
    Review AnyConnect profile XML files (typically stored in C:\Program Files\Cisco\Cisco AnyConnect Secure Mobility Client\Profile\ or within user-accessible locations) for any IPC-related settings. Check Windows Event Logs for AnyConnect-related events that may indicate IPC channel usage. Look for any evidence of the file move functionality being accessible.
    Affected if The IPC channel feature is enabled and accessible to non-privileged users, allowing the file move operation that constitutes the vulnerability.

A system is affected if Cisco AnyConnect Secure Mobility Client is installed with a version matching 2.0.0343 through 4.1(8) AND non-privileged local users can access or interact with the AnyConnect IPC channel or installation directory.

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-supplied patch or upgrade to a version beyond 4.1(8) that addresses the source-path validation flaw in the IPC channel. As a workaround, restrict local user access to the AnyConnect installation directories and monitor for suspicious file operations.

Fix this in Anyconnect Secure Mobility Client Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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