CVE-2014-6757
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 Koran - AlqoranVideos (aka com.alqoran.videos.example) application 1.0 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 'Koran - AlqoranVideos' version 1.0 fails to validate X.509 certificates when establishing SSL/TLS connections, allowing man-in-the-middle attackers to intercept traffic by presenting fraudulent certificates and obtain sensitive 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= 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 app is installedCheck the device for 'Koran - AlqoranVideos' or package name containing 'allqoranvideos' or 'alqoranvideos' using: `adb shell pm list packages | grep -i alqoran` or via Android Settings > AppsAffected if The app is present on the device
-
Check the installed versionRun `adb shell dumpsys package <package_name>` and look for versionName or versionCode, or check in Android Settings > Apps > [App Name] > VersionAffected if Version equals 1.0 or versionCode 1 - the only affected version
-
Verify SSL certificate validation behaviorUse a proxy like Burp Suite or OWASP ZAP to intercept traffic from the app. Configure the device to trust the proxy's certificate, then observe if the app accepts the proxy's fraudulent certificate without warning or errorAffected if The app successfully establishes HTTPS connections through the proxy without certificate validation errors, indicating it does not validate the certificate chain
-
Check for certificate pinning in app codeDecompile the APK using jadx or apktool and search the source for 'TrustManager', 'X509TrustManager', 'certificate pinning', or 'setHostnameVerifier' - if none validate certificates properly, the app is vulnerableAffected if No proper TrustManager implementation or certificate pinning is found in the app code
If the app 'Koran - AlqoranVideos' version 1.0 is installed and makes HTTPS network requests without rejecting invalid certificates, 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 certificate pinning or a custom TrustManager that validates the certificate chain, and ensure all network communications use validated HTTPS connections.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6757 — 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-6757 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