CVE-2014-6705
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 Maher Zain (aka com.vanagas.app.maher_zain) application 1.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 Maher Zain Android application version 1.1 fails to validate X.509 certificates from SSL/TLS servers, allowing attackers to intercept encrypted communications via man-in-the-middle attacks. The app accepts any certificate presented by a server, enabling spoofing and sensitive data exfiltration.
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.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 Maher Zain app installationCheck if the Maher Zain Android application is installed on the device. On Android, use a package manager or app info utility to list installed packages and search for 'Maher Zain' or 'maherzain'.Affected if The app is present on the device and was obtained from an untrusted source.
-
Check installed version numberView the app's version information in the device's application settings (Settings > Apps > Maher Zain > Version) or use a package info tool to query PackageInfo.versionName. The affected version is 1.1.Affected if The installed version is exactly 1.1.
-
Verify SSL/TLS usage in appAnalyze the app's network traffic or inspect the application code (APK) for SSL/TLS implementation. Look for HttpURLConnection, HttpsURLConnection, or network security configuration files.Affected if The app makes HTTPS connections but performs no certificate validation.
-
Test certificate validation behaviorConfigure a man-in-the-middle proxy with a self-signed or invalid certificate and attempt to intercept the app's HTTPS traffic. Observe whether the app accepts the invalid certificate and completes the connection.Affected if The app accepts invalid, self-signed, or mismatched SSL/TLS certificates without warning or error.
You are affected if the Maher Zain Android app version 1.1 is installed and it accepts invalid or self-signed SSL/TLS certificates during HTTPS connections.
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 chain validation and hostname verification in all network connections, preferably using certificate pinning for critical endpoints.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6705 — 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-6705 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