CVE-2014-7085
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 i Newspaper (aka com.independent.thei) application @7F080184 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 i Newspaper Android application fails to validate X.509 certificates from SSL servers, allowing man-in-the-middle attackers to intercept and manipulate SSL/TLS communications by presenting forged 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= \@7f080184CVSS 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 the installed version of i Newspaper appOn the Android device, go to Settings > Apps > i Newspaper (or Independent I Newspaper) and check the Version or Version Name field. Alternatively, use adb: `adb shell pm list packages | grep newspaper` then `adb shell dumpsys package <packagename>` to find version info.Affected if Version matches the build identifier \@7f080184 or is an unknown/older version that lacks proper SSL validation.
-
Confirm the app makes network requestsReview app permissions and traffic. The i Newspaper app fetches news content remotely, requiring network access. Use a network proxy or packet capture to observe if the app makes HTTPS requests.Affected if The app transmits data over network connections, which would be vulnerable to interception.
-
Test SSL/TLS certificate validationSet up a man-in-the-middle proxy (such as Burp Suite or OWASP ZAP) with an untrusted or self-signed certificate. Attempt to intercept traffic from the i Newspaper app while it makes network requests.Affected if The app accepts the untrusted certificate and completes connections without validation errors, indicating the SSL validation flaw is present.
-
Check for certificate pinningInspect the app's network security configuration or decompile the APK to examine the SSL/TLS implementation for certificate pinning code. Look for custom TrustManager implementations or pinning libraries.Affected if No certificate pinning is implemented, and the app uses default trust mechanisms that fail to validate certificates properly.
If the i Newspaper Android app version \@7f080184 (or an earlier unpatched version) is installed and accepts untrusted SSL certificates during network communication, the environment is affected by this CVE.
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 application, including chain-of-trust verification and hostname validation, or use certificate pinning for sensitive endpoints.
- Consultation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7085 — 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-7085 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