Anyconnect Secure Mobility ClientApplication · Cisco
CVE-2012-3094
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 · uneditedThe VPN downloader in the download_install component in Cisco AnyConnect Secure Mobility Client 3.1.x before 3.1.00495 on Linux accepts arbitrary X.509 server certificates without user interaction, which allows remote attackers to obtain sensitive information via vectors involving an invalid certificate, aka Bug ID CSCua11967.
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 VPN downloader in Cisco AnyConnect Secure Mobility Client 3.1.x before 3.1.00495 on Linux fails to properly validate X.509 server certificates during the download_install process. The client accepts arbitrary server certificates without user interaction, enabling a remote man-in-the-middle attacker to present a malicious certificate and intercept sensitive VPN credentials or session data.
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.1.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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 if Cisco AnyConnect is installed on LinuxCheck for the presence of AnyConnect binaries or packages. Common locations: /opt/cisco/anyconnect/ or look for 'anyconnect' in dpkg/rpm package listings using 'dpkg -l | grep anyconnect' or 'rpm -qa | grep anyconnect'Affected if AnyConnect client is installed on Linux
-
Determine the installed AnyConnect version on LinuxRun the anyconnect binary with version flag, typically './anyconnect --version' or check /opt/cisco/anyconnect/AnyConnectLocalPolicy.xml for version information, or use 'dpkg -s <packagename>' or 'rpm -qi <packagename>'Affected if Version cannot be determined or is 3.1.x before 3.1.00495
-
Compare installed version against affected rangeIf version is obtained, verify it falls within 3.1.x before 3.1.00495. Note that version 3.1.0 is explicitly listed as affected.Affected if Installed version is 3.1.0 or any 3.1.x version prior to 3.1.00495
-
Determine if the download_install process is usedThe vulnerability affects the VPN downloader during download_install process. Check if the client is configured to download VPN profiles or components from a server during initial connection. Inspect AnyConnect profile XML files in /opt/cisco/anyconnect/ or ~/.anyconnect/Affected if Download_install functionality is enabled or used on the Linux client
A Linux system is affected if it has Cisco AnyConnect version 3.1.0 or any 3.1.x version prior to 3.1.00495 installed and uses the VPN downloader/download_install feature.
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.1.00495 or later on all Linux endpoints. Until patched, avoid using VPN on untrusted networks.
Fix this in Anyconnect Secure Mobility Client
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3094 — 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-3094 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