CVE-2014-5733
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 Shop Love (aka com.waterwish.shoplove) application 1.05 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 Shop Love Android application version 1.05 fails to validate X.509 certificates when establishing SSL/TLS connections, enabling man-in-the-middle attackers to intercept sensitive data by presenting fraudulent certificates.
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.05CVSS 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.
-
Verify Shop Love app version 1.05 is installedOn the Android device, go to Settings > Apps > Apps, locate 'Shop Love' or 'Water Wish Shop Love', and check the version number displayed under the app nameAffected if The installed version is exactly 1.05
-
Confirm the app makes network connectionsUse Android's built-in data usage monitor (Settings > Network & Internet > Data Usage > App Data Usage) or a network analysis tool to observe if Shop Love transmits data over the networkAffected if The app establishes outbound network connections to external servers
-
Verify the app handles sensitive data over networkUse the app to perform typical actions such as logging in, browsing products, or making a purchase, and observe if personal credentials, payment information, or other sensitive data are transmittedAffected if The app transmits login credentials, payment details, or personal information over the network
-
Test for improper certificate validationConfigure a man-in-the-middle proxy (such as Burp Suite or OWASP ZAP) with a self-signed certificate on the same network, then attempt to intercept traffic from the Shop Love app while it connects to its serversAffected if The app successfully establishes SSL/TLS connections and transmits data without rejecting the invalid certificate, indicating certificate validation is not properly implemented
You are affected if Shop Love version 1.05 is installed on your Android device and the app transmits sensitive data over network connections without properly validating SSL/TLS certificates.
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 a TrustManager that verifies the certificate chain and hostname, and consider 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-5733 — 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-5733 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