CVE-2017-15340
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 · uneditedHuawei smartphones with software of TAG-AL00C92B168 have an information disclosure vulnerability. An attacker tricks the user to install a crafted application, this application simulate click action to back up data in a non-encrypted way using an Android assist function. Successful exploit could result in information disclosure.
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 · moderate confidenceA malicious application installed on Huawei smartphones (TAG-AL00C92B168) exploits Android's assist function to simulate user click actions, automatically triggering non-encrypted data backups that expose sensitive information to the attacker.
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= tag-al00c92b168CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 device modelCheck if the device is a Huawei Tag Al00 smartphone. On Android, go to Settings > About Phone > Model Number, or run `getprop ro.product.model` via ADB.Affected if The device model is not Huawei Tag Al00, as this vulnerability only affects that specific model.
-
Verify firmware versionCheck the build/firmware version. On Android, go to Settings > About Phone > Build Number, or run `getprop ro.build.display.id` via ADB.Affected if The firmware version is exactly tag-al00c92b168. Only this specific build is affected by this CVE.
-
Confirm assist feature is enabledCheck if Android's assist or voice assistant function is enabled. Go to Settings > Apps > Default Apps > Assist App, or check Settings > Google > Search & Assistant. Run `settings get secure assist` via ADB if available.Affected if The assist/assistant feature is enabled and can be invoked by applications, as the exploit leverages this function to simulate clicks.
-
Check app installation permissionsVerify if the device allows installation from unknown sources (sideloading). Go to Settings > Security > Install unknown apps, or check if 'Unknown sources' is enabled in Settings > Apps.Affected if Users can install applications from sources other than the official app store, as the attack requires a malicious application to be installed first.
The device is affected only if it is a Huawei Tag Al00 with firmware version tag-al00c92b168 AND the assist function is accessible to applications AND a malicious app can be installed on the device.
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 dataUsers should avoid sideloading applications from untrusted sources; organizations should enforce mobile device management policies restricting app installation. The vendor (Huawei) should release a patch to secure the assist function backup workflow or enforce encryption.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15340 — 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-2017-15340 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