How severe is CVE-2022-31754?

CVE-2022-31754 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2022-31754 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (44th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2022-31754?

CVE-2022-31754 primarily affects Huawei Emui. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2022-31754?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2022-31754 published?

CVE-2022-31754 was published on 2022-06-13 and last updated on 2026-06-17.

CVE-2022-31754

CVE-2022-31754 is a high-severity vulnerability in Huawei Emui with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 1% (44th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Huawei Emui
Published: 2022-06-13
Last modified: 2026-06-17

Description

Logical defects in code implementation in some products. Successful exploitation of this vulnerability may affect the availability of some features.

Frequently asked questions

What is CVE-2022-31754?: Logical defects in code implementation in some products. Successful exploitation of this vulnerability may affect the availability of some features.
How severe is CVE-2022-31754?: CVE-2022-31754 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2022-31754 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (44th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-31754?: CVE-2022-31754 primarily affects Huawei Emui. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2022-31754?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2022-31754 published?: CVE-2022-31754 was published on 2022-06-13 and last updated on 2026-06-17.

References

https://consumer.huawei.com/en/support/bulletin/2022/6/

Affected products (3)

cpe:2.3:o:huawei:emui:10.1.0:*:*:*:*:*:*:*
cpe:2.3:o:huawei:emui:12.0.0:*:*:*:*:*:*:*
cpe:2.3:o:huawei:magic_ui:3.1.0:*:*:*:*:*:*:*

More vulnerabilities in Huawei Emui

CVE-2023-52381 — Critical (CVSS 9.8): Script injection vulnerability in the email module.Successful exploitation of this vulnerability may affect service…
CVE-2023-52378 — Critical (CVSS 9.8): Vulnerability of incorrect service logic in the WindowManagerServices module.Successful exploitation of this…
CVE-2023-52370 — Critical (CVSS 9.8): Stack overflow vulnerability in the network acceleration module.Successful exploitation of this vulnerability may cause…
CVE-2023-52103 — Critical (CVSS 9.8): Buffer overflow vulnerability in the FLP module. Successful exploitation of this vulnerability may cause out-of-bounds…
CVE-2023-46773 — Critical (CVSS 9.8): Permission management vulnerability in the PMS module. Successful exploitation of this vulnerability may cause…
CVE-2023-44116 — Critical (CVSS 9.8): Vulnerability of access permissions not being strictly verified in the APPWidget module.Successful exploitation of this…

All CVEs affecting Huawei Emui →