dbcve.org
Ath FirmwareOperating system · Huawei

CVE-2016-4575

MEDIUM · 6.1 CVSS v3.0 Published 2016-05-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Cross-site scripting (XSS) vulnerability in the email APP in Huawei PLK smartphones with software AL10C00 before AL10C00B211 and AL10C92 before AL10C92B211; ATH smartphones with software AL00C00 before AL00C00B361, CL00C92 before CL00C92B361, TL00HC01 before TL00HC01B361, and UL00C00 before UL00C00B361; CherryPlus smartphones with software TL00C00 before TL00C00B553, UL00C00 before UL00C00B553, and TL00MC01 before TL00MC01B553; and RIO smartphones with software AL00C00 before AL00C00B360 allows remote attackers to inject arbitrary web script or HTML via an email message.

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 confidence

The email application in multiple Huawei smartphone models fails to properly sanitize email message content, allowing remote attackers to inject arbitrary JavaScript or HTML that executes when users view malicious emails. This stored XSS vulnerability affects the email app's rendering of email body content.

MitigationUpdate affected smartphone software to versions AL10C00B211 or later (PLK), AL00C00B361 or later (ATH), TL00C00B553/UL00C00B553/TL00MC01B553 or later (CherryPlus), and AL00C00B360 or later (RIO). Users should avoid opening emails from untrusted sources until patched.

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
Ath FirmwareOperating system
Affected:= al00c00= cl00c92= tl00hc01= ul00c00
AthHardware / appliance
Affected:all versions
Rio FirmwareOperating system
Affected:= al00c00
Plk FirmwareOperating system
Affected:= al10c00= al10c92
Cherryplus FirmwareOperating system
Affected:= tl00c00= tl00mc01= ul00c00
CherryplusHardware / appliance
Affected:all versions

CVSS 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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Huawei device model
    Go to Settings > About Phone > Model Number to determine if the device is Ath, Rio, Plk, or Cherryplus
    Affected if The device model is not one of these four models (Ath, Rio, Plk, Cherryplus)
  2. Check the firmware version on Huawei Ath devices
    Go to Settings > About Phone > Version number. Compare the displayed firmware version against: al00c00, cl00c92, tl00hc01, ul00c00, or any version if firmware is listed as 'all versions'
    Affected if The firmware version exactly matches al00c00, cl00c92, tl00hc01, ul00c00, or if the device is listed as 'all versions' affected
  3. Check the firmware version on Huawei Rio devices
    Go to Settings > About Phone > Version number. Compare the displayed firmware version against: al00c00
    Affected if The firmware version exactly matches al00c00
  4. Check the firmware version on Huawei Plk devices
    Go to Settings > About Phone > Version number. Compare the displayed firmware version against: al10c00 or al10c92
    Affected if The firmware version exactly matches al10c00 or al10c92
  5. Check the firmware version on Huawei Cherryplus devices
    Go to Settings > About Phone > Version number. Compare the displayed firmware version against: tl00c00, tl00mc01, ul00c00, or any version if firmware is listed as 'all versions'
    Affected if The firmware version exactly matches tl00c00, tl00mc01, or ul00c00, or if the device is listed as 'all versions' affected

The device is affected if it is a Huawei Ath, Rio, Plk, or Cherryplus model with a firmware version matching one of the specific versions listed (al00c00, cl00c92, tl00hc01, ul00c00, al10c00, al10c92, tl00c00, tl00mc01) or if it is an Ath or Cherryplus variant marked as 'all versions'.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected smartphone software to versions AL10C00B211 or later (PLK), AL00C00B361 or later (ATH), TL00C00B553/UL00C00B553/TL00MC01B553 or later (CherryPlus), and AL00C00B360 or later (RIO). Users should avoid opening emails from untrusted sources until patched.

Fix this in Ath Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-4575 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-4575 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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