CVE-2014-7021
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 Leg Surgery - Kids Games (aka com.harriskerioe.legsurgery) application 1.0.2 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 Leg Surgery - Kids Games Android application (version 1.0.2) fails to validate X.509 certificates when establishing SSL/TLS connections. This classic certificate validation vulnerability allows man-in-the-middle attackers to intercept communications by presenting malicious certificates, enabling sensitive data exfiltration.
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.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 installed app versionUse 'adb shell pm list packages' to find the package, then 'adb shell dumpsys package <package_name>' to see versionName and versionCode. Alternatively, check Google Play Store listing or APK metadata.Affected if versionName equals 1.0.2 or versionCode equals 1
-
Extract and inspect APK for SSL/TLS codePull the APK from the device using 'adb pull /data/app/<package_name>.apk'. Use apktool, jadx, or similar to decompile and examine the source code, particularly looking for custom TrustManager, HostnameVerifier, or SSLSocketFactory implementations.Affected if Custom TrustManager accepts all certificates or skips chain validation (e.g., TrustManager that returns empty array for getAcceptedIssuers, or throws no exceptions on invalid certificates)
-
Search for insecure network connection patternsIn decompiled code, search for HttpsURLConnection, SSLContext, or HttpClient usage. Check if certificate validation is explicitly disabled or bypassed in the connection setup code.Affected if Code shows sslSocketFactory set to a factory that does not validate certificates, or hostnameVerifier accepts all hosts
A user is affected if they have version 1.0.2 of Leg Surgery - Kids Games installed and the app transmits sensitive data over network connections using the vulnerable SSL/TLS implementation.
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 dataThe application code must be updated to properly validate the entire certificate chain against trusted certificate authorities, or implement certificate pinning for known server certificates. The app should be rebuilt and republished to address this vulnerability.
- 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-7021 — 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-7021 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