CVE-2014-6711
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 ABC Lounge Webradio (aka com.nobexinc.wls_66087017.rc) application 3.3.10 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 ABC Lounge Webradio Android application version 3.3.10 fails to validate X.509 certificates from SSL servers, meaning it does not verify certificate chain, validity, or hostname matching. This allows an attacker positioned on the same network to intercept SSL/TLS communications by presenting a fraudulent certificate, enabling sensitive data interception and session hijacking.
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= 3.3.10CVSS 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 ABC Lounge Webradio versionOpen Android Settings > Apps > ABC Lounge Webradio (or Nobexrc Abc Lounge Webradio) and check the Version field under App Info. Alternatively, use 'adb shell dumpsys package com.abc.lounge.webradio' (package name may vary) to retrieve versionInfo.Affected if The displayed version is exactly 3.3.10.
-
Verify SSL certificate validation exists in codeDecompile the APK using apktool or similar. Search for custom TrustManager implementations (grep 'TrustManager' or 'X509TrustManager') and examine the implementation for proper chain validation.Affected if The TrustManager implementation accepts all certificates without validation, or the implementation is missing entirely.
-
Check for insecure HostnameVerifierIn decompiled code, search for 'HostnameVerifier' and examine if any implementation uses ALLOW_ALL_HOSTNAME_VERIFIER or equivalent logic that skips hostname matching.Affected if Hostname verification is disabled or bypassed.
-
Inspect network security configurationCheck AndroidManifest.xml and any network_security_config.xml for trust anchors or cleartext traffic settings that may permit unvalidated connections.Affected if The app is configured to trust all certificates or allows cleartext to SSL endpoints.
A user is affected if they have ABC Lounge Webradio version 3.3.10 installed and the app code contains TrustManager or HostnameVerifier implementations that bypass 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 SSL certificate validation using Android's standard TrustManager or implement certificate pinning to ensure the app only accepts the legitimate server's certificate, preventing MITM attacks.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6711 — 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-6711 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