CVE-2014-6867
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 Sortir en Alsace (aka com.axessweb.sortirenalsace) application 0.5b 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 'Sortir en Alsace' version 0.5b 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= 0.5bCVSS 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 application is installedOn the Android device, navigate to Settings > Apps > All Apps and search for 'Sortir en Alsace' or 'Sortir En Alsace'. Alternatively, use ADB: adb shell pm list packages | grep -i sortirAffected if The application 'Sortir en Alsace' is found installed on the device
-
Verify the installed versionIn Settings > Apps > All Apps > Sortir en Alsace, note the version number displayed under the app name. Alternatively, use ADB: adb shell dumpsys package com.example.sortir en alsace (replace package name if different) or check the APK file metadataAffected if The installed version is exactly 0.5b
-
Determine if the application uses network connectivityReview the app's permissions in Settings > Apps > Permissions. Check for INTERNET permission. Use a network analyzer or check if the app makes outbound connections when usedAffected if The application has INTERNET permission and makes network requests, as the vulnerability affects SSL/TLS connections used by the app
-
Inspect SSL/TLS implementation in app code (if APK available)Decompile the APK using tools like apktool or jadx. Search source code for TrustManager implementations, hostname verification (HostnameVerifier), and certificate validation logic. Look for custom TrustManager that accepts all certificatesAffected if The code contains a TrustManager that accepts all certificates or disables hostname verification, indicating certificate validation is bypassed
The user is affected if the application 'Sortir en Alsace' version 0.5b is installed and uses network connections, as the app fails to validate X.509 certificates during SSL/TLS handshakes.
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 dataThe application must be updated to implement proper SSL certificate validation using a TrustManager that validates the certificate chain, hostname verification, and certificate expiration.
- 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-6867 — 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-6867 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