dbcve.org
Anyconnect Secure Mobility ClientApplication · Cisco

CVE-2013-1130

MEDIUM · 6.8 CVSS v2.0 Published 2013-09-20
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
Cisco AnyConnect Secure Mobility Client on Mac OS X uses weak permissions for a library directory, which allows local users to gain privileges via a crafted library file, aka Bug ID CSCue33619.

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 Cisco AnyConnect Secure Mobility Client for Mac OS X stores library files in a directory with overly permissive access controls. A local unprivileged user can place a malicious library in this directory to be loaded by the AnyConnect process, achieving privilege escalation to the application's elevated context.

MitigationIdentify the library directory used by Cisco AnyConnect and correct file permissions to prevent unprivileged users from writing to or modifying it. Restrict directory access to root or the application service account only.

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:all versions

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. Determine if Cisco AnyConnect is installed on Mac OS X
    Open Terminal and run: ls /Applications | grep -i anyconnect, or check /Applications folder for Cisco AnyConnect Secure Mobility Client
    Affected if AnyConnect is present on the system
  2. Locate the library directory used by AnyConnect
    Examine the AnyConnect application bundle contents: ls -la /Applications/Cisco\ AnyConnect\ Secure\ Mobility\ Client.app/Contents/Frameworks/ or inspect the application for dynamic library paths it loads
    Affected if A library loading directory exists within the AnyConnect installation
  3. Verify permissions on the library directory
    Run ls -ld on the identified library directory to check owner, group, and permissions (e.g., ls -ld /Applications/Cisco\ AnyConnect\ Secure\ Mobility\ Client.app/Contents/Frameworks/)
    Affected if The directory permissions allow unprivileged users (others write bit set, or weak group permissions) to write or modify files
  4. Test write access as unprivileged user
    As a non-root user, attempt to create a test file in the library directory: touch /Applications/Cisco\ AnyConnect\ Secure\ Mobility\ Client.app/Contents/Frameworks/test_write 2>&1
    Affected if The write operation succeeds, indicating unprivileged users can place files in the directory
  5. Check for existing unexpected library files
    List all .dylib or .so files in the library directory and verify they are legitimate Cisco components
    Affected if Unexpected or unfamiliar library files exist that were not part of a clean installation

If Cisco AnyConnect is installed and the library directory permissions allow unprivileged users to write or modify files, the system is vulnerable to local privilege escalation via library injection.

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

Identify the library directory used by Cisco AnyConnect and correct file permissions to prevent unprivileged users from writing to or modifying it. Restrict directory access to root or the application service account only.

Fix this in Anyconnect Secure Mobility Client Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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