CVE-2014-6810
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 RIMS 2014 Annual Conference (aka com.coreapps.android.followme.rims2014) application 6.0.7.4 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 RIMS 2014 Annual Conference Android application (version 6.0.7.4) fails to validate X.509 certificates from SSL/TLS servers during HTTPS connections. This allows man-in-the-middle attackers to intercept communications by presenting fraudulent certificates, enabling them to spoof legitimate servers and capture sensitive data transmitted by the application.
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= 6.0.7.4CVSS 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 the RIMS 2014 Annual Conference app is installedOn Android, use a package manager command or app info screen to list installed applications and locate 'Core Apps Rims 2014 Annual Conference' or check the app version in Settings > Apps > App InfoAffected if The app version listed is 6.0.7.4 exactly
-
Confirm the installed version matches the vulnerable releaseView the app version in the application details screen or via package manager output (e.g., 'adb shell dumpsys package <package_name>' to retrieve versionName and versionCode)Affected if The version displayed is 6.0.7.4
-
Test SSL/TLS certificate validation behaviorConfigure a man-in-the-middle proxy (such as Burp Suite or OWASP ZAP) with an invalid or self-signed certificate, then route the device's traffic through the proxy and attempt to use the app's network featuresAffected if The app successfully establishes HTTPS connections and functions normally when presented with an invalid certificate, indicating certificate validation is not being performed
-
Verify proper certificate chain validation is absentUse network traffic analysis tools (such as Wireshark or the MITM proxy) to inspect whether the app validates the server certificate chain against trusted root CAsAffected if The app accepts connections to the server without rejecting certificates that fail chain-of-trust validation
If the RIMS 2014 Annual Conference app version 6.0.7.4 is installed and successfully connects when presented with invalid or untrusted SSL/TLS certificates, the environment is affected by this vulnerability.
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 SSL/TLS certificate validation in the application, including certificate chain verification and hostname validation. Consider implementing certificate pinning for added security.
- 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-6810 — 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-6810 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