CVE-2025-31175

Deserialization mismatch vulnerability in the DSoftBus module Impact: Successful exploitation of this vulnerability may affect service integrity.

Published: 2025-04-07 Last update: 2025-05-07 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-31175 is rated Moderate Risk (48.9/100): CVSS High severity, with low exploitation likelihood (EPSS 0.21%). Review affected assets and schedule remediation.

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-2025-31175

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-05-18 0.27% 0.21% -0.05%
2 2026-05-17 0.23% 0.27% +0.04%
3 2026-05-16 — 0.23% —

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-31175

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.4 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/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:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big 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.
 2.5 5.9 [email protected]
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
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:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2025-31175

Affected software / configurations for CVE-2025-31175

Vendor Product Version Raw CPE
huawei emui 12.0.0 cpe:2.3:o:huawei:emui:12.0.0:*:*:*:*:*:*:*
huawei emui 13.0.0 cpe:2.3:o:huawei:emui:13.0.0:*:*:*:*:*:*:*
huawei emui 14.0.0 cpe:2.3:o:huawei:emui:14.0.0:*:*:*:*:*:*:*
huawei harmonyos 2.0.0 cpe:2.3:o:huawei:harmonyos:2.0.0:*:*:*:*:*:*:*
huawei harmonyos 2.1.0 cpe:2.3:o:huawei:harmonyos:2.1.0:*:*:*:*:*:*:*
huawei harmonyos 3.0.0 cpe:2.3:o:huawei:harmonyos:3.0.0:*:*:*:*:*:*:*
huawei harmonyos 3.1.0 cpe:2.3:o:huawei:harmonyos:3.1.0:*:*:*:*:*:*:*
huawei harmonyos 4.0.0 cpe:2.3:o:huawei:harmonyos:4.0.0:*:*:*:*:*:*:*

References for CVE-2025-31175

cvelogic Threat Intelligence