Anyconnect Secure Mobility ClientApplication · Cisco
CVE-2012-2496
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 · uneditedA certain Java applet in the VPN downloader implementation in the WebLaunch feature in Cisco AnyConnect Secure Mobility Client 3.x before 3.0 MR7 on 64-bit Linux platforms does not properly restrict use of Java components, which allows remote attackers to execute arbitrary code via a crafted web site, aka Bug ID CSCty45925.
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 confidenceThe Cisco AnyConnect Secure Mobility Client 3.x before 3.0 MR7 on 64-bit Linux contains a Java applet in the WebLaunch VPN downloader feature that fails to properly restrict the use of Java components, allowing a malicious web page to execute arbitrary code through the applet.
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
= 3.0CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify AnyConnect installation on LinuxCheck for Cisco AnyConnect client by looking for the installation directory (typically /opt/cisco/anyconnect/) or by running 'ls -la /opt/cisco/anyconnect/'Affected if The client is installed in /opt/cisco/anyconnect/ on a 64-bit Linux system
-
Determine installed versionRun 'cat /opt/cisco/anyconnect/VERSION.txt' or check the About dialog in the client GUI to find the exact version numberAffected if The version is 3.0 or any 3.x version before 3.0 MR7
-
Verify Linux architectureRun 'uname -m' or 'dpkg --print-architecture' to confirm the system is 64-bit (x86_64 or amd64)Affected if The architecture returns x86_64 or amd64 (the vulnerability only affects 64-bit Linux)
-
Check WebLaunch feature statusLook for Java applet components in the AnyConnect WebLaunch directory, typically under /opt/cisco/anyconnect/weblaunch/ or check client profile settings for WebLaunch enablementAffected if WebLaunch VPN downloader feature is enabled and Java applets are permitted in the browser
A system is affected only if it is running Cisco AnyConnect 3.0 (or 3.x before 3.0 MR7) on 64-bit Linux with the WebLaunch feature enabled and Java applets allowed in the browser.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Cisco AnyConnect Secure Mobility Client to version 3.0 MR7 or later on all 64-bit Linux deployments.
Fix this in Anyconnect Secure Mobility Client
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2496 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-2496 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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