CVE-2014-7339
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 Cuanto Conoces A un Amigo (aka com.makeitpossible.CuantoConocesAunAmigo) application 2.0 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 'Cuanto Conoces A un Amigo' (version 2.0) fails to validate X.509 certificates from SSL servers, enabling man-in-the-middle attackers to spoof legitimate servers and intercept sensitive data transmitted between the app and backend services.
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= 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 the vulnerable app is installedOn the Android device, go to Settings > Apps > Downloaded or All Apps, and search for 'Cuanto Conocas A Un Amigo' or 'Makeitpossible Cuanto Conocas A Un Amigo'. Alternatively, use ADB with command: pm list packages | grep -i cuantoAffected if The package name containing 'cuanto' and 'amigo' from Makeitpossible is found on the device
-
Verify the installed version numberIn Settings > Apps > [App Name], view the Version information. The affected version is exactly 2. Compare your installed version against this value.Affected if The installed version is exactly 2.0 or simply version 2
-
Check if the app has network communication permissionsIn Settings > Apps > [App Name] > Permissions, verify if the app has permissions for Internet, Network, or similar network access capabilities.Affected if The app has network/Internet permissions enabled, meaning it can transmit data and the SSL validation flaw is exploitable
-
Inspect network traffic configurationFor security teams with access to the APK: decompile the app and examine the network security implementation in the source code, specifically looking for TrustManager implementations or custom X509TrustManager instances that may be accepting all certificates.Affected if The APK analysis reveals custom TrustManager code that does not perform proper certificate chain validation or accepts all certificates unconditionally
You are affected if the app 'Cuanto Conoces A Un Amigo' version 2 from Makeitpossible is installed on your Android device and has network communication capabilities, as the lack of SSL certificate validation can be exploited to intercept any sensitive data the app transmits.
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 Android application, preferably through certificate pinning or comprehensive trust manager configuration to ensure the app only accepts valid certificates from expected servers.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.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,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7339 — 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-7339 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