CVE-2014-6797
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 Abu Ali Anasheeds (aka com.faapps.abuali_anasheeds) 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 Android application 'Abu Ali Anasheeds' version 1.1 fails to validate X.509 certificates when establishing SSL/TLS connections, enabling man-in-the-middle attackers to intercept traffic by presenting fraudulent certificates and capture sensitive data transmitted to backend servers.
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 if Abu Ali Anasheeds app is installedOn the Android device, go to Settings > Apps > All Apps and look for 'Abu Ali Anasheeds', or use ADB command: pm list packages | grep -i anasheedsAffected if The app is present on the device
-
Check installed version of the appIn Settings > Apps > All Apps > Abu Ali Anasheeds, view the Version information; or use ADB: dumpsys package com.anasheeds | grep versionNameAffected if The version displayed is exactly 1.1
-
Confirm the app handles sensitive data over networkObserve network traffic or review the app's permissions in Settings > Apps > Permissions - look for INTERNET permission and any permissions indicating sensitive data access (like camera, contacts, location, storage)Affected if The app has INTERNET permission and accesses sensitive data (credentials, payment info, personal info) which would be transmitted insecurely
-
Verify SSL certificate validation is absentUse a network proxy tool (like Burp Suite or OWASP ZAP) to intercept SSL traffic from the device - attempt to present a self-signed certificate; if the app connects without warning or rejection, certificate validation is missingAffected if The app accepts invalid or self-signed certificates without user warning during HTTPS connections
You are affected if the Abu Ali Anasheeds app version 1.1 is installed on an Android device and accepts invalid SSL/TLS certificates, allowing sensitive transmitted data to be intercepted by attackers on the same network.
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 X.509 certificate validation in all SSL/TLS network communications, preferably using certificate pinning for known trusted endpoints, and ensure all HTTPS connections reject invalid or untrusted certificates.
- 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-6797 — 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-6797 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