CVE-2014-7452
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 Shaklee Product Catalog (aka com.wProductCatalog) 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 Shaklee Product Catalog Android application version 2.0 fails to validate X.509 certificates from SSL servers, allowing man-in-the-middle attackers to intercept encrypted communications by presenting arbitrary crafted 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= 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 Shaklee Product Catalog app is installedOn the Android device, go to Settings > Apps > Applications Manager, then search for 'Shaklee Product Catalog' or 'Shaklee' in the installed applications list. Alternatively, use adb command: `adb shell pm list packages | grep -i shaklee`Affected if The package named 'com.shaklee.productcatalog' or similar Shaklee-related package is found on the device
-
Determine the installed application versionIn Settings > Apps > Application Manager, tap on the Shaklee Product Catalog app, then look for the 'Version' or 'Version info' field showing the version number (such as 2.0 or 2.x). If using adb, run: `adb shell dumpsys package com.shaklee.productcatalog | grep versionName`Affected if The version shown is 2.0 specifically, indicating the vulnerable version listed in the CVE
-
Verify the SSL certificate validation behavior (if app is accessible for testing)Since this is a client-side vulnerability in the Android app itself, proper detection requires examining the app's network security implementation. If you have access to the APK, tools like jadx can decompile to inspect whether certificate chain validation and hostname verification are properly implemented in the network codeAffected if The app code shows missing or improper X.509 certificate validation logic (no certificate chain verification, no hostname validation, or TrustManager that accepts all certificates)
A user is affected if the Shaklee Product Catalog Android application version 2.0 is installed and the app does not properly validate SSL/TLS certificates, making encrypted communications vulnerable to man-in-the-middle interception.
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 application, including verification of the certificate chain and hostname validation, or use certificate pinning for sensitive 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-7452 — 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-7452 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