CVE-2014-7357
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 Grandparenting is Great (aka com.app_gig.layout) application 1.400 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 Grandparenting is Great Android application version 1.400 fails to verify X.509 certificates from SSL servers during HTTPS connections. This missing certificate validation allows man-in-the-middle attackers to intercept communications by presenting a fraudulent certificate, enabling spoofing of legitimate servers and theft of sensitive data transmitted through the app.
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.4CVSS 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.
-
Confirm the app is installedOn the Android device, go to Settings > Apps > Apps, and search for 'Grandparenting Is Great' or 'Bfac Grandparenting Is Great'. Alternatively, use ADB: adb shell pm list packages | grep -i grandparentAffected if The app 'Grandparenting Is Great' by Bfac appears in the installed applications list
-
Identify the installed versionIn Settings > Apps > Apps > Grandparenting Is Great, view the 'App info' or 'Version' field. Alternatively, use ADB: adb shell dumpsys package com.bfac.grandparenting | grep versionName (replace package name if different)Affected if The displayed version is 1.4 or 1.400
-
Verify the app has network permissionsCheck the app's manifest for INTERNET permission. Use ADB: adb shell dumpsys package com.bfac.grandparenting | grep -i permission, or decompile the APK and inspect AndroidManifest.xml for <uses-permission android:name="android.permission.INTERNET"/>Affected if The app holds INTERNET permission and makes network requests
-
Confirm HTTPS traffic handlingUse a network proxy (such as Burp Suite or OWASP ZAP) to intercept traffic from the device. Configure the device to trust the proxy's certificate and observe whether the app accepts connections without certificate validation errors or warningsAffected if The app successfully connects to servers over HTTPS when presented with an invalid or self-signed certificate from the proxy
The user is affected if the Grandparenting Is Great Android app version 1.4 is installed and makes HTTPS connections without proper SSL certificate validation.
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 X.509 certificate chain validation in all network connections, including hostname verification and validation against the device's trusted CA store, or implement certificate pinning for known trusted endpoints.
- Consultation1.0 h
- Implementation4.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 $2,768.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7357 — 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-7357 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