CVE-2022-31760
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 · uneditedDialog boxes can still be displayed even if the screen is locked in carrier-customized USSD services. Successful exploitation of this vulnerability may affect data integrity and confidentiality.
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 vulnerability in carrier-customized USSD (Unstructured Supplementary Service Data) services allows dialog boxes to be displayed even when the device screen is locked. This could enable attackers to perform social engineering attacks, display fake prompts, or extract sensitive information from users by presenting deceptive dialogs on a locked screen.
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= 10.1.0= 10.1.1= 11.0.0= 12.0.0= 2.0= 3.1.0= 3.1.1= 4.0.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 the installed OS versionGo to Settings > About Phone on the Huawei device and locate the version number (Emui, Harmonyos, or Magic Ui)Affected if The version shown matches exactly 10.1.0, 10.1.1, 11.0.0, or 12.0.0 for Emui; 2.0 for Harmonyos; or 3.1.0, 3.1.1, or 4.0.0 for Magic Ui
-
Confirm the USSD service is activeCheck if the device can send USSD codes (dial *#*#<code>##*#* or contact the mobile carrier to verify USSD support is provisioned on the SIM)Affected if USSD service is provisioned and functional on the device
-
Test for dialog display on lock screenLock the device screen, then have the carrier send a USSD query or trigger a USSD code. Observe whether a dialog box appears while the screen remains lockedAffected if A USSD dialog box appears on the locked screen
The device is affected if it runs one of the listed versions AND USSD service is active AND USSD dialogs display on the lock screen.
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 dataCarriers should implement proper screen-lock state checks in their USSD handling code to prevent dialogs from displaying when the screen is locked. Users should be cautious of any unexpected dialogs and avoid entering sensitive information.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31760 — 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-2022-31760 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