CVE-2018-7925
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 radio module of some Huawei smartphones Emily-AL00A The versions before 8.1.0.171(C00) have a lock-screen bypass vulnerability. An unauthenticated attacker could start third-part input method APP through certain operations to bypass lock-screen by exploit this vulnerability.
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 confidenceLock-screen bypass vulnerability in Huawei smartphone Emily-AL00A radio module versions prior to 8.1.0.171(C00). An unauthenticated attacker can start third-party input method applications through specific radio module operations to bypass the lock screen and gain unauthorized device access.
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< 8.1.0.171\(c00\)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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:P/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is Emily-AL00ACheck the device settings or use *#*#2846579#*#* to access Huawei's engineering menu and verify the model number displays as Emily-AL00A or AL00AAffected if Device model is anything other than Emily-AL00A - this vulnerability is specific to that model
-
Identify radio module firmware versionAccess Settings > About Phone > Version information or use *#*#2846579#*#* > ProjectMenu > Background Setting > RF Desktop Test > Mobile Network to view the radio/baseband versionAffected if Unable to retrieve radio module version information
-
Compare radio module version to affected rangeCompare the installed radio module version number to 8.1.0.171(C00) - versions below this threshold are vulnerableAffected if Radio module version is 8.1.0.171(C00) or higher - these versions include the patch
-
Verify third-party input methods are presentCheck Settings > Language & Input > Keyboard & Input Methods to see if any third-party input method apps are installed and enabledAffected if Only default/system input methods are available - the exploit requires a third-party input method to be accessible
Device is affected only if it is an Emily-AL00A model with radio module version prior to 8.1.0.171(C00) and has a third-party input method installed/enabled that could be triggered via the radio module.
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 data8.1.0.171
Update affected Huawei Emily-AL00A devices to firmware version 8.1.0.171(C00) or later to patch the radio module vulnerability.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7925 — 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-2018-7925 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