CVE-2014-6890
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 CouponCabin - Coupons & Deals (aka com.couponcabin) application 3.6 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 CouponCabin Android app version 3.6 fails to validate X.509 certificates from SSL servers, allowing man-in-the-middle attackers to intercept encrypted communications by presenting fraudulent certificates. This enables sensitive data exposure through a classic SSL/TLS certificate validation bypass.
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= 3.6CVSS 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 CouponCabin Android app is installedOn the Android device, go to Settings > Apps > Apps manager and search for 'CouponCabin' or 'Couponcabin Coupons & Deals', or use ADB command: adb shell pm list packages | grep -i couponAffected if The app named 'Couponcabin Coupons & Deals' or similar CouponCabin variant is present on the device
-
Determine the installed version of CouponCabinIn Settings > Apps > App info for CouponCabin, note the version name and version number displayed under 'App version', or use ADB: adb shell dumpsys package <package_name> | grep versionNameAffected if The version listed is exactly 3.6 or falls within the 3.6.x version range for this specific app
-
Test for certificate validation bypass via MITM proxyConfigure a network proxy (such as Burp Suite or OWASP ZAP) on a test device with the CouponCabin app installed. Install the proxy CA certificate on the device. Launch the CouponCabin app and attempt to load content. Inspect proxy logs to see if the app accepts connections despite the proxy presenting a certificate not matching the original server hostnameAffected if The app successfully loads content through the proxy without certificate validation errors, indicating SSL/TLS certificate validation is bypassed
-
Verify certificate chain validation is disabledDecompile the APK using tools like jadx or apktool. Examine the source code for implementations of TrustManager, HostnameVerifier, or custom SSLContext creation. Look for code that implements custom X509TrustManager that accepts all certificates or disables hostname verificationAffected if The APK contains a custom TrustManager that accepts all certificates (e.g., trusting all X509 certificates without proper validation) or a HostnameVerifier that returns true for all hostnames
A user is affected if the CouponCabin Android app version 3.6 is installed and the app accepts SSL connections with invalid or mismatched certificates, indicating certificate validation is not properly implemented.
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 certificate validation including hostname verification and certificate chain trust validation, or preferably certificate pinning for critical endpoints.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6890 — 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-6890 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