CVE-2014-6660
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 Koleksi Hadis Nabi SAW (aka com.wKoleksiHadisNabiSAW) application 0.1 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 'Koleksi Hadis Nabi SAW' version 0.1 fails to validate X.509 certificates from SSL/TLS servers, allowing man-in-the-middle attackers to intercept encrypted communications by presenting a crafted (likely self-signed or fraudulent) certificate. This enables credential theft, session hijacking, and injection of malicious content into what should be encrypted channels.
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= 0.1CVSS 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 the vulnerable app is installedOn the Android device, go to Settings > Apps > Downloaded, or use 'adb shell pm list packages' to list all installed packages. Look for an app named 'Koleksi Hadis Nabi SAW' or related to Blogkamek.Affected if The app 'Koleksi Hadis Nabi SAW' by Blogkamek is found on the device.
-
Verify the installed versionIn Settings > Apps > [Koleksi Hadis Nabi SAW], check the version listed under 'App info' or 'Version'. Alternatively, use 'adb shell dumpsys package [package_name]' to get version details.Affected if The version displayed is exactly 0.1.
-
Confirm the app makes network requestsMonitor network traffic from the device while using the app, using tools like packet capture or Android's built-in netstat. Check if the app connects to remote servers.Affected if The app transmits data over network connections.
-
Inspect APK for disabled SSL validation (if APK is available)If you have access to the APK file, decompile it using tools like apktool or jadx. Search the source code for patterns that disable SSL validation, such as: TrustManager implementations that accept all certificates, hostname verification being disabled (setDefaultHostnameVerifier with empty verifier), or SSLContext with trusting all trust managers.Affected if Code contains implementations that bypass or disable X.509 certificate chain validation.
You are affected if the app 'Koleksi Hadis Nabi SAW' version 0.1 is installed on your device and it makes network requests 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 certificate pinning or validating the full certificate chain including hostname verification. Use Android's built-in certificate validation mechanisms and avoid disabling SSL validation for any reason.
- 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-6660 — 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-6660 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