dbcve.org
Emily Al00a FirmwareOperating system · Huawei

CVE-2019-5282

HIGH · 7.8 CVSS v3.1 Published 2019-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
Bastet module of some Huawei smartphones with Versions earlier than Emily-AL00A 9.0.0.182(C00E82R1P21), Versions earlier than Emily-TL00B 9.0.0.182(C01E82R1P21), Versions earlier than Emily-L09C 9.0.0.203(C432E7R1P11), Versions earlier than Emily-L29C 9.0.0.203(C432E7R1P11), Versions earlier than Emily-L29C 9.0.0.202(C185E2R1P12) have a double free vulnerability. An attacker tricks the user into installing a malicious application, which frees on the same memory address twice. Successful exploit could result in malicious code execution.

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

A double free vulnerability exists in the Bastet module of certain Huawei smartphones (Emily-AL00A, Emily-TL00B, Emily-L09C, Emily-L29C). An attacker tricks users into installing a malicious application that frees the same memory address twice, which can lead to arbitrary code execution.

MitigationUpdate the device firmware to the patched versions (Emily-AL00A 9.0.0.182/C00E82R1P21, Emily-TL00B 9.0.0.182/C01E82R1P21, Emily-L09C 9.0.0.203/C432E7R1P11, Emily-L29C 9.0.0.203/C432E7R1P11 or later) and avoid installing applications from untrusted sources.

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
Emily Al00a FirmwareOperating system
Affected:< emily-al00a_9.0.0.182\(c00e82r1p21\)
Emily Tl00b FirmwareOperating system
Affected:< emily-tl00b_9.0.0.182\(c01e82r1p21\)
Emily L09c FirmwareOperating system
Affected:< emily-l09c_9.0.0.203\(c432e7r1p11\)
Emily L29c FirmwareOperating system
Affected:< emily-l29c_9.0.0.203\(c432e7r1p11\)< emily-l29c_9.0.0.202\(c185e2r1p12\)< emily-l29c_9.0.0.207\(c636e7r1p13\)< emily-l29c_9.0.0.205\(c635e2r1p11\)
Hima L09ca FirmwareOperating system
Affected:< hima-l09ca_9.0.0.198\(c432e10r1p16\)
Hima L29ca FirmwareOperating system
Affected:< hima-l29ca_9.0.0.198\(c432e10r1p16\)
Hima L29c FirmwareOperating system
Affected:< hima-l29c_9.0.0.204\(c636e10r2p1\)

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 device model
    Check the device settings or use 'AT+CGMM' or 'AT+CGSN' commands via UART or serial debug to confirm the model number is one of: Emily-AL00A, Emily-TL00B, Emily-L09C, Emily-L29C, Hima-L09ca, Hima-L29ca, or Hima-L29c
    Affected if Device model matches one of the listed affected model numbers
  2. Check firmware version for Emily-AL00A
    Navigate to Settings > About Phone > Version or use 'AT+HVER' command to retrieve firmware version; compare against emily-al00a_9.0.0.182(c00e82r1p21)
    Affected if Firmware version is lower than 9.0.0.182(c00e82r1p21)
  3. Check firmware version for Emily-TL00B
    Navigate to Settings > About Phone > Version or use 'AT+HVER' command; compare against emily-tl00b_9.0.0.182(c01e82r1p21)
    Affected if Firmware version is lower than 9.0.0.182(c01e82r1p21)
  4. Check firmware version for Emily-L09C or L29C
    Navigate to Settings > About Phone > Version or use 'AT+HVER' command; for L09C compare against emily-l09c_9.0.0.203(c432e7r1p11); for L29C compare against the applicable version (9.0.0.203, 9.0.0.202, 9.0.0.207, or 9.0.0.205 depending on build)
    Affected if Firmware version is lower than the respective patched version for that variant
  5. Check firmware version for Hima variants
    Navigate to Settings > About Phone > Version or use 'AT+HVER' command; for Hima-L09ca/L29ca compare against hima-l09ca_9.0.0.198(c432e10r1p16); for Hima-L29c compare against hima-l29c_9.0.0.204(c636e10r2p1)
    Affected if Firmware version is lower than the respective patched version for that Hima variant

The device is affected if it is one of the listed Huawei model variants AND its firmware version is below the specified patched version for that model.

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 the device firmware to the patched versions (Emily-AL00A 9.0.0.182/C00E82R1P21, Emily-TL00B 9.0.0.182/C01E82R1P21, Emily-L09C 9.0.0.203/C432E7R1P11, Emily-L29C 9.0.0.203/C432E7R1P11 or later) and avoid installing applications from untrusted sources.

Fix this in Emily Al00a Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5282 — 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-2019-5282 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