Anyconnect Secure Mobility ClientApplication · Cisco
CVE-2012-2499
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 IPsec implementation in Cisco AnyConnect Secure Mobility Client 3.0 before 3.0.08057 does not verify the certificate name in an X.509 certificate, which allows man-in-the-middle attackers to spoof servers via a crafted certificate, aka Bug ID CSCtz26985.
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 IPsec implementation in Cisco AnyConnect Secure Mobility Client versions before 3.0.08057 fails to verify the certificate name field in X.509 certificates during the authentication handshake. This allows an attacker positioned on the network path to present a specially crafted certificate with a different subject name, causing the client to trust a malicious server and enabling man-in-the-middle attacks.
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.0= 3.0.0629= 3.0.07059CVSS 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
- None
AV:N/AC:M/Au:N/C:P/I:P/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 the installed Cisco AnyConnect Secure Mobility Client versionLocate the AnyConnect client installation and retrieve its version number (commonly found in the client GUI about section, or via the installer properties on Windows systems)Affected if The installed version matches 3.0, 3.0.0629, or 3.0.07059, or falls within the range before 3.0.08057
-
Confirm IPsec VPN profile is configuredCheck if AnyConnect is configured to use IPsec as the tunneling protocol (this can be verified in the AnyConnect profile XML configuration or VPN connection settings)Affected if IPsec is the active VPN protocol for the connection profile in use
-
Verify certificate-based authentication is enabledExamine the authentication settings for the IPsec connection profile to confirm certificate authentication is configured as the authentication methodAffected if Certificate-based authentication is the configured authentication mechanism for the IPsec VPN
-
Confirm the connection is vulnerable during handshakeObserve that the client accepts the server certificate without validating the subject name field during the TLS/IPsec handshake phaseAffected if The client completes the connection without performing proper certificate name (subject) validation
A user is affected if they are running AnyConnect version 3.0 through 3.0.07059 with IPsec and certificate-based authentication enabled, as the client will not validate the certificate name field during the authentication handshake.
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.08057 or later which includes proper certificate name verification.
Fix this in Anyconnect Secure Mobility Client
Scoped from the published advisory
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2499 — 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-2499 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