CVE-2014-6792
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 Suriname Radio (aka com.wordbox.surinameRadio) application 1.5 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 Suriname Radio Android application version 1.5 fails to validate X.509 certificates when establishing SSL/TLS connections. This allows man-in-the-middle attackers to intercept traffic by presenting fraudulent certificates, enabling credential theft, session hijacking, and injection of malicious content.
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.5CVSS 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 installed Suriname Radio appOn Android device: Settings > Apps > find 'Suriname Radio'. On computer: use ADB command 'adb shell pm list packages' or check installed APKsAffected if Package named 'suriname.radio' or similar is present
-
Check installed versionIn Settings > Apps > Suriname Radio > Version info, or use 'adb shell dumpsys package suriname.radio' to retrieve versionName and versionCodeAffected if Version equals 1.5 exactly (versionName='1.5' or versionCode corresponding to 1.5)
-
Verify certificate validation behavior (if APK available)Decompile APK using apktool or similar, then search source code for TrustManager implementations, setHostnameVerifier calls, or ALLOW_ALL_HOSTNAME_VERIFIER constants indicating disabled validationAffected if Code shows certificate validation is disabled or improperly implemented (e.g., empty TrustManager, ALLOW_ALL_VERIFIER)
-
Inspect network traffic for SSL issuesUse a network proxy (e.g., Burp Suite, OWASP ZAP) to intercept traffic from the app. Observe if the app accepts the proxy's certificate without warning or errorAffected if App connects successfully through proxy without certificate warnings, indicating it accepts untrusted certificates
If the Suriname Radio Android app version 1.5 is installed and accepts certificates from untrusted sources without proper X.509 validation, the environment is affected by this CVE.
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 built-in certificate handling or a properly configured TrustManager. Avoid disabling certificate validation and consider certificate pinning for sensitive endpoints.
- 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-6792 — 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-6792 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