CVE-2016-3677
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 Huawei Wear App application before 15.0.0.307 for Android does not validate SSL certificates, which allows local users to have unspecified impact via unknown vectors, aka HWPSIRT-2016-03008.
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 Huawei Wear App for Android versions prior to 15.0.0.307 fails to validate SSL certificates during HTTPS connections, allowing an attacker on the same network to perform man-in-the-middle attacks and intercept or modify encrypted traffic between the app and its server.
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 dataall versionsall versionsCVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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 installed Huawei appsOn the Android device, navigate to Settings > Apps or use 'adb shell pm list packages | grep huawei' to list installed Huawei applicationsAffected if Either the Huawei Wear App or Huawei Hilink App package is present on the device
-
Check Huawei Wear App versionIn Settings > Apps > Huawei Wear, view the Version information; alternatively, use 'adb shell dumpsys package com.huawei.wearable' to retrieve version detailsAffected if The displayed version is earlier than 15.0.0.307 or if the version cannot be determined (all versions prior to the fix are affected)
-
Check Huawei Hilink App versionIn Settings > Apps > Huawei Hilink, view the Version information; alternatively, use 'adb shell dumpsys package com.huawei.android.e3d' or search for the Hilink package nameAffected if The Huawei Hilink App is installed (all versions are affected according to the advisory)
-
Verify SSL certificate validation behaviorConfigure a proxy such as Burp Suite or OWASP ZAP on a test device, install the device CA certificate, and attempt to intercept traffic from the app; observe if the app permits the connection without certificate validation errorsAffected if The app successfully communicates through the proxy without SSL validation errors, indicating the vulnerability is present
You are affected if the Huawei Wear App version is below 15.0.0.307, or if the Huawei Hilink App is installed at any version, as both fail to validate SSL certificates.
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 dataUpdate the Huawei Wear App to version 15.0.0.307 or later, which implements proper SSL certificate validation. For enterprise environments, also consider implementing additional controls like network segmentation to limit local attacker proximity.
- Consultation2.0 h
- Implementation8.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,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3677 — 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-2016-3677 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