CVE-2020-9149
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 · uneditedAn application error verification vulnerability exists in a component interface of Huawei Smartphone. Local attackers can exploit this vulnerability to modify and delete user SMS messages.
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 confidenceThis is a local input validation/access control vulnerability in a Huawei Smartphone component interface that handles SMS messages. The flaw allows a local attacker with device access to bypass application error verification and modify or delete user SMS data.
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.0.0= 10.1.0= 10.1.1= 11.0.0= 3.0.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 device OS versionGo to Settings > About Phone on the Huawei smartphone and locate the EMUI or Magic UI version field. Alternatively, use the command 'getprop ro.build.version.emui' or 'getprop ro.build.version.magic' via ADB shell.Affected if The displayed version is exactly 10.0.0, 10.1.0, 10.1.1, or 11.0.0 for EMUI, or exactly 3.0.0, 3.1.0, 3.1.1, or 4.0.0 for Magic UI.
-
Confirm SMS component is accessibleVerify that the SMS/Messaging application is installed and functional on the device. Attempt to access the default SMS application through the device launcher or by using the command 'content query --uri content://sms/' via ADB shell if permissions allow.Affected if SMS application is present and accessible without additional security restrictions.
-
Check for security patch levelGo to Settings > About Phone > Software Information and check the Security Patch level date. Alternatively, use the command 'getprop ro.build.version.security_patch' via ADB shell.Affected if The Security Patch level is dated before the Huawei patch release for CVE-2020-9149, or the patch level field is empty or outdated.
A device is affected if it runs EMUI versions 10.0.0, 10.1.0, 10.1.1, or 11.0.0, or Magic UI versions 3.0.0, 3.1.0, 3.1.1, or 4.0.0, and has not received the corresponding security patch for this SMS input validation flaw.
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 dataApply the Huawei security patch for CVE-2020-9149 via device software updates. Users should ensure their Huawei smartphones are running the latest firmware version provided by the manufacturer.
- Consultation2.0 h
- Testing3.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9149 — 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-2020-9149 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