CVE-2022-39071

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.

Published: 2023-05-30 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-39071 is rated Low Risk (35.9/100): CVSS High severity, with low exploitation likelihood (EPSS 0.29%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-39071

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.06% 0.29% +0.23%
2 2026-06-09 0.15% 0.06% -0.09%
3 2026-06-01 — 0.15% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-39071

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.1 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.2 [email protected]
7.1 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.2 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2022-39071

Affected software / configurations for CVE-2022-39071

Vendor Product Version Raw CPE
zte blade_a52_firmware < m02 cpe:2.3:o:zte:blade_a52_firmware:*:*:*:*:*:*:*:*
zte blade_a51_firmware < m07 cpe:2.3:o:zte:blade_a51_firmware:*:*:*:*:*:*:*:*
zte blade_a3_lite_firmware < m09 cpe:2.3:o:zte:blade_a3_lite_firmware:*:*:*:*:*:*:*:*
zte blade_a5_2020_firmware < m05 cpe:2.3:o:zte:blade_a5_2020_firmware:*:*:*:*:*:*:*:*
zte blade_l210_firmware < 1.14 cpe:2.3:o:zte:blade_l210_firmware:*:*:*:*:*:*:*:*
zte blade_a7s_firmware < 2.2 cpe:2.3:o:zte:blade_a7s_firmware:*:*:*:*:*:*:*:*
zte blade_a31_firmware < m03 cpe:2.3:o:zte:blade_a31_firmware:*:*:*:*:*:*:*:*
zte blade_a31_plus_firmware < m04 cpe:2.3:o:zte:blade_a31_plus_firmware:*:*:*:*:*:*:*:*
zte blade_a5_2019_firmware < m13 cpe:2.3:o:zte:blade_a5_2019_firmware:*:*:*:*:*:*:*:*
zte blade_a71_firmware < 2.4 cpe:2.3:o:zte:blade_a71_firmware:*:*:*:*:*:*:*:*
zte blade_a72_firmware < 11.0.3 cpe:2.3:o:zte:blade_a72_firmware:*:*:*:*:*:*:*:*
zte blade_v20_smart_firmware < 1.14 cpe:2.3:o:zte:blade_v20_smart_firmware:*:*:*:*:*:*:*:*
zte blade_v30_firmware < 1.11 cpe:2.3:o:zte:blade_v30_firmware:*:*:*:*:*:*:*:*
zte blade_v30_vita_firmware < 1.11 cpe:2.3:o:zte:blade_v30_vita_firmware:*:*:*:*:*:*:*:*
zte v40_pro_firmware < 11.0.4_9046 cpe:2.3:o:zte:v40_pro_firmware:*:*:*:*:*:*:*:*
zte blade_v40_vita_firmware < 11.0.2_8045 cpe:2.3:o:zte:blade_v40_vita_firmware:*:*:*:*:*:*:*:*
zte axon_40_ultra_firmware < 1.0.0b26 cpe:2.3:o:zte:axon_40_ultra_firmware:*:*:*:*:*:*:*:*

References for CVE-2022-39071

cvelogic Threat Intelligence