CVE-2014-5526
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 Inmobi library 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 Inmobi library for Android fails to validate X.509 certificates during SSL/TLS handshakes, allowing man-in-the-middle attackers to intercept communications by presenting arbitrary crafted certificates and thereby obtain sensitive information.
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 dataall versionsCVSS 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.
-
Locate the Inmobi library in the applicationDecompile the Android APK and search for Inmobi-related files (typically inmobi*.jar, inmobi*.aar, or classes containing 'inmobi' in the package name). Alternatively, examine the app's build configuration (build.gradle, libs folder) for inmobi dependencies.Affected if The Inmobi library is present in the application package.
-
Confirm network traffic uses Inmobi for SSL/TLS connectionsUse a network proxy (such as Burp Suite or OWASP ZAP) to intercept traffic from the Android device or emulator running the app. Look for SSL/TLS connections to Inmobi endpoints (typically *.inmobi.com) that succeed without proper certificate validation failures.Affected if The application makes SSL/TLS requests to Inmobi servers and connections are established without certificate validation errors.
-
Inspect the library code for certificate validation logicDecompile the Inmobi library JAR/AAR and examine classes handling HTTPS connections. Look for custom TrustManager,HostnameVerifier, or SSLSocketFactory implementations. Search for code that disables SSL validation (for example, TrustManager that accepts all certificates).Affected if The library contains code that bypasses or disables X.509 certificate chain validation.
-
Test for MITM vulnerability with invalid certificateConfigure a network proxy with an untrusted or self-signed SSL certificate. Attempt to intercept traffic from the application. If the app successfully connects through the proxy without certificate warnings or failures, validation is not properly enforced.Affected if The application accepts invalid or untrusted SSL certificates during MITM testing.
If the Inmobi library is present in the Android application and SSL/TLS connections to Inmobi servers succeed without proper certificate validation (visible through MITM testing or code inspection), the application is affected by CVE-2014-5526.
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 dataUpdate to a patched version of the Inmobi library that implements proper X.509 certificate chain validation, or implement certificate pinning in the application as a compensating control.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5526 — 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-5526 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