CVE-2014-5758
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 Yellow Pages Local Search (aka com.yellowbook.android2) application 11.0.0 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 Yellow Pages Local Search Android application version 11.0.0 fails to validate X.509 certificates from SSL servers during HTTPS connections. This allows man-in-the-middle attackers to intercept encrypted traffic by presenting fraudulent certificates, enabling spoofing of legitimate servers and theft of sensitive data.
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= 11.0.0CVSS 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 if Yellow Pages Local Search app is installedOn the Android device, go to Settings > Apps > All Apps and look for 'Yellow Pages Local Search' or 'Yellowbook', or use ADB command: adb shell pm list packages | grep -i yellowAffected if The app is not found in the installed applications list, then this CVE does not apply to your environment
-
Retrieve the installed application versionIn Settings > Apps > Yellow Pages Local Search, scroll to the 'Version' or 'Version info' field; alternatively, use ADB: adb shell dumpsys package com.yellowpages.local (replace with actual package name if different)Affected if Version information cannot be retrieved or the app is not present
-
Compare the installed version to the affected rangeCheck if the version listed is exactly 11.0.0 as specified in the affected productsAffected if The installed version is 11.0.0, the device is vulnerable to certificate validation bypass via MITM attacks on HTTPS connections
-
Confirm HTTPS traffic handling (optional context check)Review if the app is used to access sensitive data over HTTPS networks; this CVE allows attackers to intercept such traffic if on a compromised networkAffected if The app handles sensitive information over HTTPS and is version 11.0.0
If Yellow Pages Local Search version 11.0.0 is installed on the Android device, the application is affected by improper SSL/TLS certificate validation and is vulnerable to man-in-the-middle attacks.
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/TLS certificate validation in the Android application, including chain-of-trust verification and hostname validation, or use certificate pinning for critical endpoints.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5758 — 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-5758 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