CVE-2014-7593
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 Mr Whippet - Yorkshire Ice (aka com.appytimes.ice) application 1.1 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 'Mr Whippet - Yorkshire Ice' (com.appytimes.ice) version 1.1 fails to validate X.509 certificates from SSL servers, allowing man-in-the-middle attackers to intercept encrypted communications 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.1CVSS 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 the app is installedOn the Android device, go to Settings > Apps > All Apps and search for 'Mr Whippet - Yorkshire Ice', or run 'adb shell pm list packages' to list installed packages and look for 'com.appytimes.ice'Affected if The package com.appytimes.ice is present on the device
-
Confirm the installed versionIn Settings > Apps > All Apps > Mr Whippet - Yorkshire Ice, note the version number displayed under the app name, or use 'adb shell dumpsys package com.appytimes.ice' and look for versionName or versionCodeAffected if The version is exactly 1.1
-
Determine if the app handles sensitive dataUse the app and observe what data it transmits over the network (login credentials, personal information, payment data). Use a network proxy like Burp Suite or ZAP to intercept traffic and identify whether SSL-encrypted connections are used for sensitive operationsAffected if The app transmits any personal, financial, or authentication data over HTTPS without proper certificate validation
-
Inspect SSL certificate validation codeIf you have the APK file, decompile it using tools like jadx or apktool. Navigate to the source code and search for HttpURLConnection, HttpsURLConnection, or OkHttpClient usage. Look for implementations that set hostname verifier or trust manager - specifically check if setHostnameVerifier or custom TrustManager are used that bypass proper validationAffected if The code contains implementations that accept any certificate (e.g., ALLOW_ALL_HOSTNAME_VERIFIER or custom TrustManager that does not validate the certificate chain)
You are affected if the Mr Whippet - Yorkshire Ice app version 1.1 (com.appytimes.ice) is installed and the app transmits sensitive data over network 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 the Android application, preferably using certificate pinning or trusted CA store validation to prevent SSL spoofing attacks.
- 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-7593 — 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-7593 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