dbcve.org
Anyconnect Secure Mobility ClientApplication · Cisco

CVE-2015-0755

MEDIUM · 6.8 CVSS v2.0 Published 2015-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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 Posture module for Cisco Identity Services Engine (ISE), as distributed in Cisco AnyConnect Secure Mobility Client 4.0(64), allows local users to gain privileges via unspecified commands, aka Bug ID CSCut05797.

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 · moderate confidence

The Posture module for Cisco Identity Services Engine (ISE), as distributed in Cisco AnyConnect Secure Mobility Client 4.0(64), contains a local privilege escalation vulnerability allowing local users to execute unspecified commands and gain elevated privileges.

MitigationApply available Cisco patches for CSCut05797. Until patched, restrict local access to the ISE posture module to trusted administrators only and monitor for suspicious local command execution.

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\(64\)

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
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:S/C:C/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 Cisco AnyConnect installation and version
    Check installed version of Cisco AnyConnect Secure Mobility Client. On Windows, inspect registry key HKLM\SOFTWARE\Cisco\Cisco AnyConnect Secure Mobility Client\ClientVersion or check C:\Program Files\Cisco\Cisco AnyConnect Secure Mobility Client. On macOS, check /Applications/Cisco/ or run 'system_profiler SPApplicationsDataType | grep -i anyconnect'. On Linux, check dpkg -l | grep anyconnect or rpm -qa | grep anyconnect.
    Affected if The installed version is exactly 4.0(64)
  2. Confirm Posture module presence
    Verify the ISE Posture module component is installed with AnyConnect. On Windows, check for Posture module DLLs in the AnyConnect installation directory (typically C:\Program Files\Cisco\Cisco AnyConnect Secure Mobility Client\). On macOS/Linux, inspect the AnyConnect modules directory for posture-related components.
    Affected if Posture module files exist in the AnyConnect installation directory
  3. Check for suspicious local processes
    Monitor running processes for unusual command execution originating from AnyConnect or ISE Posture module paths. Use tasklist (Windows) or ps (macOS/Linux) to list processes and look for unexpected child processes spawned by AnyConnect binaries.
    Affected if Unexpected or unauthorized processes are running under AnyConnect or Posture module contexts with elevated privileges
  4. Review local user permissions on Posture module
    Check file system permissions on the Posture module directories and executables. Ensure only trusted administrators have write or execute permissions. On Windows, use icacls or Properties > Security. On Unix systems, use ls -la.
    Affected if Non-privileged local users have modify or execute permissions on Posture module components

Environment is affected if Cisco AnyConnect Secure Mobility Client version 4.0(64) is installed with the Posture module enabled, as this specific version contains the privilege escalation vulnerability in the ISE Posture component.

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 available Cisco patches for CSCut05797. Until patched, restrict local access to the ISE posture module to trusted administrators only and monitor for suspicious local command execution.

Fix this in Anyconnect Secure Mobility Client Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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