CVE-2014-6936
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 IDS 2013 (aka de.mobileeventguide.ids2013) application 1.21 for Android does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.
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 IDS 2013 Android application version 1.21 fails to verify X.509 certificates from SSL servers, allowing man-in-the-middle attackers to intercept and modify encrypted communications by presenting fraudulent certificates.
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= 1.21CVSS 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
- Adjacent
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:A/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 if IDS 2013 app is installedOn the Android device, go to Settings > Apps > All Apps, and search for 'IDS 2013', 'Mobileeventguide Ids 2013', or 'Mobile Event Guide'. Alternatively, use ADB: `adb shell pm list packages | grep -i ids`Affected if The package name contains 'mobileeventguide' or 'ids' and the app is present on the device
-
Check installed version equals 1.21In Settings > Apps > All Apps, tap on the IDS 2013 app and view the Version information under 'App info'. Alternatively, use ADB: `adb shell dumpsys package <package_name> | grep versionName`Affected if The displayed version is exactly 1.21 (no other version is affected)
-
Verify the app uses network connectionsWhile the app is running, use ADB to monitor network activity: `adb shell netstat -an | grep <package_name>` or check in Settings > Apps > App info > Data usage that network access is permittedAffected if The app establishes outgoing network connections, as the vulnerability only matters when the app communicates over network
-
Inspect SSL certificate verification in app codeObtain the APK file (from Play Store or device), decompile it using apktool, and examine the source code for SSL/TLS implementation. Look for implementations using HttpsURLConnection, HttpClient, or OkHttp and check if certificate verification is properly implemented with TrustManager or if it is disabled/bypassedAffected if The app code either lacks proper certificate chain validation or explicitly disables verification (e.g., TrustManager that accepts all certificates)
You are affected only if the IDS 2013 / Mobileeventguide Ids 2013 Android app version 1.21 is installed AND it makes network connections without proper X.509 certificate validation.
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 dataImplement proper X.509 certificate chain validation and consider certificate pinning in the application, or update to a patched version that enforces SSL/TLS certificate verification.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2014-6936 — 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-2014-6936 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