CVE-2014-6805
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 weibo (aka magic.weibo) application 1.2 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 weibo (magic.weibo) Android application version 1.2 fails to verify X.509 certificates from SSL servers during HTTPS connections. This allows man-in-the-middle attackers on the same network to intercept traffic, spoof legitimate servers, and capture sensitive information such as authentication credentials or user data.
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.2CVSS 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 Weibo app is installedOn the Android device, go to Settings > Apps > Applications Manager and look for 'Weibo' or 'magic.weibo' in the installed applications list. Alternatively, run 'adb shell pm list packages' to list all installed packages and grep for 'weibo' or 'magic.weibo'.Affected if The Weibo (magic.weibo) Android application is installed on the device
-
Check installed Weibo versionIn Settings > Apps > Weibo, view the App info or version details. Alternatively, use 'adb shell dumpsys package magic.weibo' to retrieve package information including the version name and version code.Affected if The installed version is exactly 1.2 (versionName = 1.2)
-
Confirm HTTPS functionality is usedThe Weibo app inherently uses HTTPS for connecting to Weibo servers to fetch feeds, post content, and authenticate users. This is standard app behavior and requires no additional configuration to trigger the vulnerability.Affected if The app makes any HTTPS connection to Weibo servers (which occurs during normal app usage for login, feed loading, posting, etc.)
If the Weibo (magic.weibo) Android app version 1.2 is installed and makes HTTPS connections, the device is affected by this vulnerability due to missing X.509 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/TLS certificate validation in the application by using a correctly configured TrustManager or certificate pinning to ensure the app only trusts valid, server-provided certificates.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6805 — 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-6805 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