CVE-2014-6667
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 racemotocross (aka com.bossappsmk.racemotocross) application 1.2 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 Android application 'racemotocross' (version 1.2) fails to validate X.509 certificates during SSL/TLS connections, allowing an attacker on the same network to intercept communications by presenting a crafted certificate. This enables man-in-the-middle attacks where sensitive data transmitted to legitimate servers can be captured or manipulated.
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.2CVSS 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 racemotocross app is installedOn the Android device, go to Settings > Apps > All Apps and search for 'racemotocross'. Alternatively, use ADB command: 'adb shell pm list packages | grep racemotocross' to list the package.Affected if The racemotocross app is present on the device.
-
Verify the installed versionIn Settings > Apps > All Apps > racemotocross, check the version number displayed. Alternatively, use ADB: 'adb shell dumpsys package com.racemotocross.app' (replace with actual package name if different) to retrieve version info.Affected if The version is 1.2.
-
Inspect SSL/TLS certificate validation in app codeDecompile the APK using tools like apktool or jadx. Navigate to the network-related classes (typically in /smali/ or /java/ directories) and search for SSLContext, TrustManager, orHostnameVerifier implementations.Affected if The app uses a custom TrustManager that accepts all certificates, or disables certificate validation (e.g., TrustManager that returns true for all checks), or uses an empty HostnameVerifier.
-
Check for proper certificate chain validationIn the decompiled code, locate any HttpClient, HttpsURLConnection, or networking library usage. Examine whether the app properly validates the certificate chain against trusted CAs or implements certificate pinning.Affected if The app does not validate the certificate chain, or contains code that bypasses SSL validation (common patterns include ALLOW_ALL_HOSTNAME_VERIFIER or custom TrustManager that accepts any certificate).
You are affected if the racemotocross app version 1.2 is installed and its code does not properly validate X.509 certificates during SSL/TLS connections.
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 certificate validation using Android's built-in certificate pinning or validating the certificate chain against trusted Certificate Authorities. All network communications should verify server certificates before establishing trusted connections.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6667 — 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-6667 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