CVE-2014-6993
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 Codeeta Coupons (aka com.codeeta.promos) application 1.0.5 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 Codeeta Coupons Android application fails to validate X.509 certificates during SSL/TLS connections, allowing attackers to perform man-in-the-middle attacks. The app accepts any certificate presented by the server, enabling spoofing and interception of sensitive data transmitted over encrypted channels.
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.0.5CVSS 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 installed Codeeta Coupons versionOn the Android device, go to Settings > Apps > Codeeta Coupons (or Codeeta Codeeta Coupons), then check the Version field under App Info. Alternatively, use ADB: adb shell pm list packages | grep codeeta, then adb shell dumpsys package <package_name> | grep versionNameAffected if The installed version is exactly 1.0.5
-
Confirm the package nameRun 'adb shell pm list packages | grep -i codeeta' to find the exact package name of the installed applicationAffected if A package containing 'codeeta' or 'coupons' is installed on the device
-
Determine if the app transmits sensitive dataReview the app's functionality: check if it handles user credentials, payment information, personal data, or any sensitive network communications by inspecting the app or its network trafficAffected if The app is used to transmit or receive sensitive user data over the network
-
Analyze SSL/TLS certificate validationAnalyze the APK file (obtain via 'adb pull /data/app/<package_name>.apk') using a decompiler or security analysis tool (e.g., jadx, APKTool) to inspect the SSL/TLS implementation. Look for custom TrustManager implementations, hostname verifiers, and whether certificate pinning is present. Search for code that accepts all certificates (e.g., TrustAllCerts, empty keystore, or ALLOW_ALL_HOSTNAME_VERIFIER)Affected if The code contains implementations that bypass SSL certificate validation or accept any certificate without proper verification
You are affected if Codeeta Coupons version 1.0.5 is installed and the app is used to transmit sensitive data, as the app fails to validate SSL/TLS certificates allowing potential man-in-the-middle attacks.
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 in the Android app, preferably through certificate pinning for known trusted endpoints or ensuring proper TrustManager implementation with full chain verification.
- Consultation1.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 $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6993 — 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-6993 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