CVE-2023-34167
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 · uneditedVulnerability of spoofing trustlists of Huawei desktop.Successful exploitation of this vulnerability can cause third-party apps to hide app icons on the desktop to prevent them from being uninstalled.
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 trustlist spoofing vulnerability in Huawei Desktop allows malicious third-party applications to manipulate the desktop trustlist mechanism, enabling them to hide their icons from the desktop interface. This prevents users from seeing and subsequently uninstalling these applications through normal desktop interactions.
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= 11.0.1= 12.0.0= 12.0.1= 13.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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Emui versionNavigate to Settings > About Phone > Version on the Huawei device, or run 'getprop ro.build.version.emui' via ADB shellAffected if The displayed Emui version matches 11.0.1, 12.0.0, 12.0.1, or 13.0.0 exactly
-
Confirm desktop trustlist feature is presentOn the Huawei desktop, examine whether the trustlist mechanism exists in the system by checking if the device uses Huawei's default launcher with the trustlist functionality under Settings > Home & Wallpaper > Home settingsAffected if The desktop trustlist feature is available and enabled on the device
-
Verify third-party app installation capabilityCheck if the device allows installation of third-party applications from unknown sources or via APK filesAffected if Third-party app installation is permitted, which would allow a malicious application to exploit the trustlist spoofing vulnerability
The device is affected if it runs Emui version 11.0.1, 12.0.0, 12.0.1, or 13.0.0 and has the desktop trustlist feature enabled, as this is the specific version range for which the vulnerability applies.
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.
dbcve · scopedAwait the official Huawei security patch for this vulnerability; no user-side workarounds are described in the available advisory material.
EMUI 13.0.1 or later (or latest available EMUI security patch level)
- 1. Check for available EMUI security updates by going to Settings > System & Updates > Software Update on your Huawei device
- 2. Ensure your device is connected to Wi-Fi and has sufficient battery before checking for updates
- 3. Download and install any available EMUI security patches or updates
- 4. After updating, verify the security patch level by going to Settings > About Phone > Version > Build Number to confirm the vulnerability is addressed
- 5. Alternatively, contact Huawei customer support for specific guidance on obtaining the security fix for this CVE
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34167 — 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-2023-34167 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