CVE-2024-47404
CVE-2024-47404 is a high-severity vulnerability in Openatom Openharmony with a CVSS 3.x base score of 8.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-415.
Key facts
- Severity: High (CVSS 3.x base score 8.4)
- EPSS exploit prediction: 0% (6th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2024-42434
- Weakness: CWE-415
- Affected product: Openatom Openharmony
- Published:
- Last modified:
Description
in OpenHarmony v4.1.0 and prior versions allow a local attacker cause the common permission is upgraded to root and sensitive information leak through double free.
Frequently asked questions
- What is CVE-2024-47404?
- in OpenHarmony v4.1.0 and prior versions allow a local attacker cause the common permission is upgraded to root and sensitive information leak through double free.
- How severe is CVE-2024-47404?
- CVE-2024-47404 has a CVSS 3.x base score of 8.4, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability high.
- Is CVE-2024-47404 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (6th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2024-47404?
- CVE-2024-47404 affects Openatom Openharmony. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2024-47404?
- 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.
- Does CVE-2024-47404 have an EU (EUVD) identifier?
- Yes. CVE-2024-47404 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-42434.
- When was CVE-2024-47404 published?
- CVE-2024-47404 was published on 2024-11-05 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:o:openatom:openharmony:*:*:*:*:-:*:*:*
More vulnerabilities in Openatom Openharmony
- CVE-2025-0304 — High (CVSS 8.8): in OpenHarmony v4.1.2 and prior versions allow a local attacker cause the common permission is upgraded to root and…
- CVE-2025-0303 — High (CVSS 8.8): in OpenHarmony v4.1.2 and prior versions allow a local attacker cause the common permission is upgraded to root and…
- CVE-2024-47398 — High (CVSS 8.8): in OpenHarmony v4.1.2 and prior versions allow a local attacker cause the device is unable to boot up through…
- CVE-2024-10074 — High (CVSS 8.8): in OpenHarmony v4.1.1 and prior versions allow a local attacker cause the common permission is upgraded to root through…
- CVE-2024-41160 — High (CVSS 8.8): in OpenHarmony v4.1.0 and prior versions allow a local attacker cause the common permission is upgraded to root and…
- CVE-2024-41157 — High (CVSS 8.8): in OpenHarmony v4.1.0 and prior versions allow a local attacker cause the common permission is upgraded to root and…
All CVEs affecting Openatom Openharmony →
Other CWE-415 (Double Free) vulnerabilities
- CVE-2018-0101 — Critical (CVSS 10.0): A vulnerability in the Secure Sockets Layer (SSL) VPN functionality of the Cisco Adaptive Security Appliance (ASA)…
- CVE-2026-8925 — Critical (CVSS 9.8): The curl logic that works with SASL authentication could end up cleaning up the GSASL context *twice* without clearing…
- CVE-2020-37239 — Critical (CVSS 9.8): libbabl 0.1.62 contains a broken double free detection vulnerability that allows attackers to bypass memory safety…
- CVE-2026-43011 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: net/x25: Fix potential double free of skb When…
- CVE-2026-31609 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: smb: client: avoid double-free in…
- CVE-2026-31608 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: smb: server: avoid double-free in…