CVE-2024-56449

Privilege escalation vulnerability in the Account module Impact: Successful exploitation of this vulnerability may affect service confidentiality.

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

CVE-2024-56449 is rated Low Risk (31.8/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.05%). 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-2024-56449

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 2025-11-04 0.02% 0.05% +0.03%
2 2025-03-17 0.09% 0.02% -0.07%
3 2025-01-14 — 0.09% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-56449

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.6 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L 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:L)
A normal user session is enough; they don’t have to be admin.
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:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.8 4.7 [email protected]
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2024-56449

Affected software / configurations for CVE-2024-56449

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:*:*:*:*:*:*:*
huawei harmonyos 4.2.0 cpe:2.3:o:huawei:harmonyos:4.2.0:*:*:*:*:*:*:*

References for CVE-2024-56449

cvelogic Threat Intelligence