in OpenHarmony v4.1.0 and prior versions allow a local attacker arbitrary code execution in pre-installed apps through out-of-bounds write.
CVE-2024-39816
Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2024-09-02. NVD baseline CVSS 8.4; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.4
- EG Score
- 8.4(medium)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity84% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 7%
- KEV
- Not listed
Published
September 2, 2024
Last Modified
September 4, 2024
References (1)
Related CVEs
Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.
Frequently asked(5)
What is CVE-2024-39816?
When was CVE-2024-39816 disclosed?
Is CVE-2024-39816 actively exploited?
What is the CVSS score of CVE-2024-39816?
How do I remediate CVE-2024-39816?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2024-39816
Is Your Infrastructure Affected by CVE-2024-39816?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.