dbcve.org
WebexApplication · Cisco

CVE-2012-6399

MEDIUM · 5.8 CVSS v2.0 Published 2013-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable No privileges 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 WebEx 4.1 on iOS does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate, aka Bug ID CSCud94176.

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 confidence

Cisco WebEx 4.1 on iOS fails to validate that the server hostname matches the certificate's Common Name (CN) or subjectAltName field during SSL/TLS handshake. This classic certificate validation bypass allows man-in-the-middle attackers to intercept encrypted traffic using any valid certificate, exposing sensitive data in transit.

MitigationImplement proper hostname verification by validating the server's certificate against the expected hostname before establishing the SSL connection. Consider additional controls like certificate pinning for enhanced security.

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
WebexApplication
Affected:= 4.1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Cisco WebEx iOS version
    On the iOS device, go to Settings > General > About > Version to see the Cisco WebEx app version, or check in the App Store/Installed Apps list for Cisco WebEx version 4.1
    Affected if The installed version is exactly 4.1 on iOS
  2. Verify SSL/TLS connectivity is enabled
    Check if the Cisco WebEx app is configured to connect to WebEx meeting servers (the app uses SSL/TLS by default for meeting connections)
    Affected if The app is configured to connect to WebEx servers over network, which uses SSL/TLS by default
  3. Confirm app is actively used or configured
    Check if there are any saved WebEx meeting sites or the app has been used to join/start meetings
    Affected if The app has been used or configured to connect to WebEx servers, triggering the vulnerable SSL/TLS handshake code path

A user is affected if they have Cisco WebEx version 4.1 installed on iOS and the app is configured to connect to WebEx servers, as the app fails to validate server hostname against the certificate, allowing MITM attacks on encrypted traffic.

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

Implement proper hostname verification by validating the server's certificate against the expected hostname before establishing the SSL connection. Consider additional controls like certificate pinning for enhanced security.

Fix this in Webex Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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