CVE-2014-6668
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 African Radios Live (aka com.nana.africanradioslive) application 1.0.6 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 African Radios Live version 1.0.6 fails to validate X.509 certificates when establishing SSL/TLS connections with backend servers. This allows man-in-the-middle attackers to intercept encrypted communications by presenting forged certificates, enabling theft of sensitive data such as credentials or personal 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 data= 1.0.6CVSS 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 African Radios Live is installedOn the Android device, go to Settings > Apps > Apps manager and search for 'African Radios Live' or 'Nana Project'. Alternatively, use adb command: pm list packages | grep -i africaAffected if The package named 'African Radios Live' or containing 'nana' and 'radio' is found installed on the device
-
Check the installed version numberIn Settings > Apps > Apps manager, tap on African Radios Live and view the Version info. The exact version number is displayed under 'Version' or 'Version name'Affected if The displayed version is exactly 1.0.6
-
Determine if the app connects to network serversWhile the app is running, use Android's built-in netstat or a network monitoring app to observe active connections. Check if the app initiates outbound SSL/TLS connections to backend radio streaming serversAffected if The app establishes network connections to remote servers (the vulnerability only applies when the app communicates over network)
-
Inspect SSL certificate validation implementationIf you have access to the app binary (APK), decompile it and examine the network code for TrustManager implementation, hostname verifier, or certificate pinning logic. Look for custom X509TrustManager implementations or null hostname verifiersAffected if The app code lacks proper X509TrustManager implementation, uses a custom TrustManager that accepts all certificates, or has no certificate validation logic at all
A user is affected if African Radios Live version 1.0.6 is installed and the app makes network connections to backend servers without proper SSL/TLS 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 the Android TrustManager or certificate pinning to verify server certificates against trusted certificate authorities before establishing secure connections.
- 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-6668 — 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-6668 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