dbcve.org
Blade A52 FirmwareOperating system · Zte

CVE-2022-39071

HIGH · 7.1 CVSS v3.1 Published 2023-05-30
Fix available
A fix is available. Upgrade to 1.14 / 2.2 or later.
See remediation →
74/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
There is an unauthorized access vulnerability in some ZTE mobile phones. If a malicious application is installed on the phone, it could overwrite some system configuration files and user installers without user permission.

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 vulnerability in ZTE mobile phones allows a maliciously crafted application to overwrite system configuration files and user installers without requiring user permission. This indicates a fundamental flaw in the Android permission model on affected ZTE devices, where application sandboxing or file system access controls are insufficiently enforced.

MitigationUsers should avoid installing applications from untrusted sources and await an official firmware patch from ZTE. Enterprise environments may need to consider mobile device management (MDM) solutions to restrict app installations.

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
Blade A52 FirmwareOperating system
Affected:< m02
Blade A51 FirmwareOperating system
Affected:< m07
Blade A3 Lite FirmwareOperating system
Affected:< m09
Blade A5 2020 FirmwareOperating system
Affected:< m05
Blade L210 FirmwareOperating system
Affected:< 1.14
Blade A7s FirmwareOperating system
Affected:< 2.2
Blade A31 FirmwareOperating system
Affected:< m03
Blade A31 Plus FirmwareOperating system
Affected:< m04

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

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

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

  1. Identify the ZTE device model
    Go to Settings > About Phone > Model Number, or check the physical device label, to confirm if the device is one of the following: Blade A52, Blade A51, Blade A3 Lite, Blade A5 2020, Blade L210, Blade A7s, Blade A31, or Blade A31 Plus
    Affected if The device model matches any of the listed affected models
  2. Check the firmware version for Blade A52
    Navigate to Settings > About Phone > Software Version, or dial *983*6642# to access the hidden test menu, and note the firmware version
    Affected if The firmware version is below m02 (for Blade A52)
  3. Check the firmware version for Blade A51
    Navigate to Settings > About Phone > Software Version, or dial *983*6642# to access the hidden test menu, and note the firmware version
    Affected if The firmware version is below m07 (for Blade A51)
  4. Check the firmware version for Blade A3 Lite
    Navigate to Settings > About Phone > Software Version, or dial *983*6642# to access the hidden test menu, and note the firmware version
    Affected if The firmware version is below m09 (for Blade A3 Lite)
  5. Check the firmware version for Blade A5 2020
    Navigate to Settings > About Phone > Software Version, or dial *983*6642# to access the hidden test menu, and note the firmware version
    Affected if The firmware version is below m05 (for Blade A5 2020)
  6. Check the firmware version for other affected models
    Navigate to Settings > About Phone > Software Version, or dial *983*6642# to access the hidden test menu, and note the firmware version
    Affected if For Blade L210: version below 1.14; for Blade A7s: below 2.2; for Blade A31: below m03; for Blade A31 Plus: below m04

The device is affected if it is a ZTE Blade model from the affected list and its current firmware version is below the specified threshold for that model.

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.

dbcve · scoped
Upgrade available Upgrade to 1.14 / 2.2 or later
Fixed in 1.142.2
Interim mitigation

Users should avoid installing applications from untrusted sources and await an official firmware patch from ZTE. Enterprise environments may need to consider mobile device management (MDM) solutions to restrict app installations.

Recommended fix Moderate confidence

Blade A52: m02 or later | Blade A51: m07 or later | Blade A3 Lite: m09 or later | Blade A5 2020: m05 or later | Blade L210: 1.14 or later | Blade A7s: 2.2 or later | Blade A31: m03 or later | Blade A31 Plus: m04 or later

  1. Identify the specific Blade model from the affected list (A52, A51, A3 Lite, A5 2020, L210, A7s, A31, or A31 Plus)
  2. Navigate to ZTE official support site (support.zte.com.cn)
  3. Locate the firmware download section for the specific Blade model
  4. Download and install the firmware version that matches or exceeds: Blade A52: m02, Blade A51: m07, Blade A3 Lite: m09, Blade A5 2020: m05, Blade L210: 1.14, Blade A7s: 2.2, Blade A31: m03, Blade A31 Plus: m04
  5. Install the firmware update following ZTE's standard OTA or manual flash procedures
  6. Verify the installed firmware version matches the fixed release
Caveat Firmware updates may reset user settings; ensure backup of data before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Blade A52 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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