CVE-2024-47291

Permission vulnerability in the ActivityManagerService (AMS) module Impact: Successful exploitation of this vulnerability may affect availability.

Published: 2024-09-27 Last update: 2024-10-01 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

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

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 2024-09-28 — 0.04% —

Full EPSS history (1 record total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.6 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:H/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:H)
They need powerful rights—admin, root, or similar—before this pays off.
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:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 0.8 4.7 [email protected]
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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: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:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2024-47291

Affected software / configurations for CVE-2024-47291

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-47291

cvelogic Threat Intelligence