dbcve.org
Agassi L09 FirmwareOperating system · Huawei

CVE-2018-7907

MEDIUM · 5.5 CVSS v3.0 Published 2018-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
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
Some Huawei products Agassi-L09 AGS-L09C100B257CUSTC100D001, AGS-L09C170B253CUSTC170D001, AGS-L09C199B251CUSTC199D001, AGS-L09C229B003CUSTC229D001, Agassi-W09 AGS-W09C100B257CUSTC100D001, AGS-W09C128B252CUSTC128D001, AGS-W09C170B252CUSTC170D001, AGS-W09C229B251CUSTC229D001, AGS-W09C331B003CUSTC331D001, AGS-W09C794B001CUSTC794D001, Baggio2-U01A BG2-U01C100B160CUSTC100D001, BG2-U01C170B160CUSTC170D001, BG2-U01C199B162CUSTC199D001, BG2-U01C209B160CUSTC209D001, BG2-U01C333B160CUSTC333D001, Bond-AL00C Bond-AL00CC00B201, Bond-AL10B Bond-AL10BC00B201, Bond-TL10B Bond-TL10BC01B201, Bond-TL10C Bond-TL10CC01B131, Haydn-L1JB HDN-L1JC137B068, Kobe-L09A KOB-L09C100B252CUSTC100D001, KOB-L09C209B002CUSTC209D001, KOB-L09C362B001CUSTC362D001, Kobe-L09AHN KOB-L09C233B226, Kobe-W09C KOB-W09C128B251CUSTC128D001, LelandP-L22C 8.0.0.101(C675CUSTC675D2), LelandP-L22D 8.0.0.101(C675CUSTC675D2), Rhone-AL00 Rhone-AL00C00B186, Selina-L02 Selina-L02C432B153, Stanford-L09S Stanford-L09SC432B183, Toronto-AL00 Toronto-AL00C00B223, Toronto-AL00A Toronto-AL00AC00B223, Toronto-TL10 Toronto-TL10C01B223 have a sensitive information leak vulnerability. An attacker can trick a user to install a malicious application to exploit this vulnerability. Due to insufficient verification of the input, successful exploitation can cause sensitive information leak.

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 confidence

This vulnerability in multiple Huawei smartphone and tablet models allows a malicious application installed by the user to bypass insufficient input validation and access sensitive information. The attack requires user participation (installing a malicious app), making it a local privilege escalation leading to information disclosure.

MitigationUsers should avoid installing applications from untrusted sources and apply Huawei security patches/firmware updates as they become available. Organizations should inventory affected devices and ensure they receive timely firmware updates.

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
Agassi L09 FirmwareOperating system
Affected:= ags-l09c100b257custc100d001= ags-l09c170b253custc170d001= ags-l09c199b251custc199d001= ags-l09c229b003custc229d001
Agassi W09 FirmwareOperating system
Affected:= ags-w09c100b257custc100d001= ags-w09c128b252custc128d001= ags-w09c170b252custc170d001= ags-w09c229b251custc229d001= ags-w09c331b003custc331d001= ags-w09c794b001custc794d001
Baggio2 U01a FirmwareOperating system
Affected:= bg2-u01c100b160custc100d001= bg2-u01c170b160custc170d001= bg2-u01c199b162custc199d001= bg2-u01c209b160custc209d001= bg2-u01c333b160custc333d001
Bond Al00c FirmwareOperating system
Affected:= bond-al00cc00b201
Bond Al10b FirmwareOperating system
Affected:= bond-al10bc00b201
Bond Tl10b FirmwareOperating system
Affected:= bond-tl10bc01b201
Bond Tl10c FirmwareOperating system
Affected:= bond-tl10cc01b131
Haydn L1jb FirmwareOperating system
Affected:= hdn-l1jc137b068

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
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 checks

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

  1. Identify device model
    Check the device settings or system information to determine the Huawei model (Agassi L09, Agassi W09, Baggio2 U01a, Bond, or Haydn)
    Affected if Model matches any of the affected products: Agassi L09, Agassi W09, Baggio2 U01a, Bond Al00c/Al10b/Tl10b/Tl10c, or Haydn L1jb
  2. Determine firmware build number
    Navigate to Settings > About Phone > Build Number, or use adb shell getprop ro.build.version.emui or similar command to retrieve the firmware version
    Affected if Firmware version exactly matches any of the listed affected versions for the identified model
  3. Verify input validation exposure
    This is a vulnerability in the platform input validation. No direct config check available - the vulnerability exists in the affected firmware versions regardless of configuration
    Affected if Device runs an affected firmware version listed in the CVE

The device is affected if it is a Huawei Agassi L09/W09, Baggio2 U01a, Bond, or Haydn model running any of the specific firmware versions enumerated in the CVE (exact version match required).

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

Users should avoid installing applications from untrusted sources and apply Huawei security patches/firmware updates as they become available. Organizations should inventory affected devices and ensure they receive timely firmware updates.

Fix this in Agassi L09 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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