CVE-2014-6922
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 KFAI Community Radio (aka com.skyblue.pra.kfai) application 2.0.4 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 KFAI Community Radio Android application version 2.0.4 fails to validate X.509 certificates from SSL servers, allowing attackers to perform man-in-the-middle attacks by presenting forged certificates. This improper SSL certificate validation enables attackers to intercept and modify encrypted communications, potentially exposing sensitive user 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= 2.0.4CVSS 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.
-
Check if KFAI Community Radio app is installedOn the Android device, go to Settings > Apps > Apps, and look for 'Listener Interactive Kfai Community Radio' in the list of installed applications. Alternatively, use ADB: adb shell pm list packages | grep kfaiAffected if The application named 'Listener Interactive Kfai Community Radio' appears in the installed applications list
-
Verify the installed version numberIn Settings > Apps > Apps > Listener Interactive Kfai Community Radio, tap on 'App info' or 'Storage' to view the version name or version number. Alternatively, use ADB: adb shell dumpsys package com.kfai.radio.listener | grep versionNameAffected if The version displayed is exactly 2.0.4
-
Confirm no security updates have been appliedCheck if there is a newer version available in the Google Play Store by searching for 'KFAI Community Radio' and comparing the listed version to 2.0.4. If a later version exists, the vulnerability may have been patched in that update.Affected if No later version is available in the Play Store, or the installed version remains at 2.0.4
If the KFAI Community Radio Android application version 2.0.4 is installed on the device with no subsequent security updates applied, the device is affected by improper 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/TLS certificate chain validation using standard Android security APIs (e.g., CertificateChainValidator, Network Security Config with certificate pinning), ensuring the app verifies certificates against trusted Certificate Authorities before establishing secure connections.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6922 — 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-6922 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