dbcve.org
Oxfords An00a FirmwareOperating system · Huawei

CVE-2021-22400

MEDIUM · 5.5 CVSS v3.1 Published 2021-08-03
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 Smartphones has an insufficient input validation vulnerability due to the lack of parameter validation. An attacker may trick a user into installing a malicious APP. The app can modify specific parameters, causing the system to crash. Affected product include:OxfordS-AN00A 10.0.1.10(C00E10R1P1),10.0.1.105(C00E103R3P3),10.0.1.115(C00E110R3P3),10.0.1.123(C00E121R3P3),10.0.1.135(C00E130R3P3),10.0.1.135(C00E130R4P1),10.0.1.152(C00E140R4P1),10.0.1.160(C00E160R4P1),10.0.1.167(C00E166R4P1),10.0.1.173(C00E172R5P1),10.0.1.178(C00E175R5P1) and 10.1.0.202(C00E79R5P1).

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

A local privilege escalation and denial of service vulnerability exists in certain Huawei smartphones (OxfordS-AN00A) where a maliciously crafted application can modify specific system parameters without proper validation, causing the system to crash.

MitigationUsers should avoid installing applications from untrusted sources. Organizations should implement MDM controls to restrict app installation and monitor for the availability of vendor patches from Huawei.

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
Oxfords An00a FirmwareOperating system
Affected:= 10.0.1.10\(c00e10r1p1\)= 10.0.1.105\(c00e103r3p3\)= 10.0.1.115\(c00e110r3p3\)= 10.0.1.123\(c00e121r3p3\)= 10.0.1.135\(c00e130r3p3\)= 10.0.1.135\(c00e130r4p1\)= 10.0.1.152\(c00e140r4p1\)= 10.0.1.160\(c00e160r4p1\)= 10.0.1.167\(c00e166r4p1\)= 10.0.1.173\(c00e172r5p1\)= 10.0.1.178\(c00e175r5p1\)= 10.1.0.202\(c00e79r5p1\)

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 checks

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

  1. Identify device model
    Check if the device is a Huawei smartphone with model identifier OxfordS-AN00A or OxfordS-AN00. This can be found in Settings > About Phone > Model Number, or via ADB with 'adb shell getprop ro.product.model'
    Affected if Device model is OxfordS-AN00A or variant containing OxfordS-AN00
  2. Determine firmware version
    Retrieve the installed firmware build number. On the device, go to Settings > About Phone > Build Number, or use ADB with 'adb shell getprop ro.build.display.id' to obtain the full version string
    Affected if Firmware version matches any of: 10.0.1.10(c00e10r1p1), 10.0.1.105(c00e103r3p3), 10.0.1.115(c00e110r3p3), 10.0.1.123(c00e121r3p3), 10.0.1.135(c00e130r3p3), 10.0.1.135(c00e130r4p1), 10.0.1.152(c00e140r4p1), 10.0.1.160(c00e160r4p1), 10.0.1.167(c00e166r4p1), 10.0.1.173(c00e172r5p1), 10.0.1.178(c00e175r
  3. Review installed applications
    Audit installed applications for any unknown or untrusted sources. Check Settings > Apps > App List, or use ADB with 'adb shell pm list packages' to enumerate installed packages
    Affected if Any application from an untrusted or unknown source is installed that has permission to modify system parameters

The device is affected if it is a Huawei OxfordS-AN00A model running one of the listed firmware versions and has an untrusted application installed that can modify system parameters.

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. Organizations should implement MDM controls to restrict app installation and monitor for the availability of vendor patches from Huawei.

Fix this in Oxfords An00a Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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