dbcve.org
Blade A52 FirmwareOperating system · Zte

CVE-2022-39075

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 delete some system files 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

This vulnerability allows a malicious application installed on affected ZTE mobile phones to delete system files without user permission. The issue appears to stem from improper permission controls or access controls on the file system, enabling a locally installed app to perform unauthorized file deletion operations that should require elevated privileges.

MitigationUsers should avoid installing applications from untrusted sources and ensure Google Play Protect is enabled. Organizations should apply any available vendor patches and consider mobile device management (MDM) policies to restrict app installation permissions.

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 ZTE Blade model
    Go to Settings > About Phone > Model Number (or Device Name) to confirm the exact Blade model (e.g., Blade A52, Blade A51, Blade A3 Lite, Blade A5 2020, Blade L210, Blade A7s, Blade A31, or Blade A31 Plus)
    Affected if The device is any of these eight Blade models
  2. Check current firmware version
    Navigate to Settings > About Phone > Software Info > Build Number (or Version) to find the installed firmware version string
    Affected if The firmware version is below the threshold for your specific model (see version list: A52<m02, A51<m07, A3 Lite<m09, A5 2020<m05, L210<1.14, A7s<2.2, A31<m03, A31 Plus<m04)
  3. Confirm Android version for context
    Go to Settings > About Phone > Android Version to note the OS version
    Affected if This is supplementary context only; the vulnerability is version-specific to the ZTE firmware regardless of Android version

A user is affected if they own a ZTE Blade A52, A51, A3 Lite, A5 2020, L210, A7s, A31, or A31 Plus device running firmware below the specified thresholds for each 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 ensure Google Play Protect is enabled. Organizations should apply any available vendor patches and consider mobile device management (MDM) policies to restrict app installation permissions.

Recommended fix High confidence

Upgrade to the following firmware versions: 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

  1. 1. Identify the exact model number of the ZTE Blade device from the Settings > About Phone menu
  2. 2. Determine the current firmware version installed on the device
  3. 3. Navigate to the ZTE support website at support.zte.com.cn or use the device's built-in system update feature
  4. 4. Check for available firmware updates for the specific Blade model
  5. 5. Download and install the appropriate fixed firmware version: Blade A52 to version m02, Blade A51 to version m07, Blade A3 Lite to version m09, Blade A5 2020 to version m05, Blade L210 to version 1.14, Blade A7s to version 2.2, Blade A31 to version m03, or Blade A31 Plus to version m04
  6. 6. Ensure the device is connected to a stable Wi-Fi network and has sufficient battery (at least 50%) before initiating the update
  7. 7. After the update completes, verify the firmware version has been successfully updated in Settings > About Phone
Caveat Firmware updates may reset some device settings; backup important data before updating

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

Fix this in Blade A52 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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