dbcve.org
Anyconnect Secure Mobility ClientApplication · Cisco

CVE-2015-0665

MEDIUM · 6.6 CVSS v2.0 Published 2015-03-17
Fix available
A fix is available. Upgrade to after 4.0 or later.
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 Hostscan module in Cisco AnyConnect Secure Mobility Client 4.0(.00051) and earlier allows local users to write to arbitrary files via crafted IPC messages, aka Bug ID CSCus79173.

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 Hostscan module in Cisco AnyConnect Secure Mobility Client 4.0(.00051) and earlier contains a local privilege escalation vulnerability where local users can write to arbitrary files via crafted IPC messages, potentially allowing privilege escalation or arbitrary code execution.

MitigationUpgrade to a patched version of Cisco AnyConnect Secure Mobility Client. Since this is a client-side vulnerability, organizations should ensure all endpoints running the affected AnyConnect client versions are identified and updated through Cisco's official update mechanism or manual patch deployment.

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.0\(.00051\)

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. Identify installed Cisco AnyConnect Client version
    Locate the Cisco AnyConnect Secure Mobility Client installation and retrieve its version information, typically found in the program's properties or about section
    Affected if The installed version is 4.0(.00051) or any earlier version within the 4.0 release line
  2. Verify Hostscan module presence
    Determine whether the Hostscan module is installed or enabled as part of the AnyConnect configuration
    Affected if Hostscan module is present and the parent AnyConnect version is 4.0(.00051) or earlier
  3. Confirm build number against affected range
    Check the exact build or revision number of the AnyConnect client executable
    Affected if The build number is at or below .00051, indicating the vulnerable version

A system is affected if Cisco AnyConnect Secure Mobility Client version 4.0(.00051) or earlier with the Hostscan module enabled is installed.

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
Upgrade available Upgrade to a release after 4.0
Interim mitigation

Upgrade to a patched version of Cisco AnyConnect Secure Mobility Client. Since this is a client-side vulnerability, organizations should ensure all endpoints running the affected AnyConnect client versions are identified and updated through Cisco's official update mechanism or manual patch deployment.

Fix this in Anyconnect Secure Mobility Client Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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