dbcve.org
OpenharmonyOperating system · Openatom

CVE-2025-24301

HIGH · 7.8 CVSS v3.1 Published 2025-03-04
Fix available
A fix is available. Upgrade to after 5.0.2 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
in OpenHarmony v5.0.2 and prior versions allow a local attacker arbitrary code execution in pre-installed apps through use after free. This vulnerability can be exploited only in restricted scenarios.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A use-after-free vulnerability in OpenHarmony v5.0.2 and prior allows a local attacker to achieve arbitrary code execution within pre-installed applications. The vulnerability stems from improper memory management where a pointer to freed memory is still referenced after deallocation, potentially allowing an attacker to manipulate memory layout and inject malicious code.

MitigationUpgrade to a patched version of OpenHarmony above v5.0.2. If upgrading is not immediately feasible, conduct code review of pre-installed applications to identify and remediate use-after-free patterns, focusing on proper pointer lifecycle management and memory deallocation handling.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenharmonyOperating system
Affected:>= 4.1.0, <= 5.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenHarmony version
    Run 'syscap' command or check /system/etc/param/ohos.version file to determine the installed OpenHarmony version number
    Affected if The installed version falls within the range of 4.1.0 through 5.0.2 inclusive
  2. Confirm pre-installed applications exist
    List the contents of /system/app or /preinstall directories to identify pre-installed applications on the device
    Affected if Pre-installed applications are present on the system
  3. Verify application sandboxing status
    Check the app privileges and sandbox configuration files in /system/etc/app/ or examine the app's manifest for sandbox enforcement status
    Affected if Applications run with elevated privileges or without proper sandboxing, increasing exploitability
  4. Review memory management in pre-installed apps
    If source code access is available, search for patterns involving free(), delete, or equivalent deallocation functions followed by further use of the freed pointer
    Affected if Use-after-free code patterns exist in pre-installed application binaries or source code

The environment is affected if OpenHarmony version is between 4.1.0 and 5.0.2 inclusive AND pre-installed applications are present on the device.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 5.0.2
Interim mitigation

Upgrade to a patched version of OpenHarmony above v5.0.2. If upgrading is not immediately feasible, conduct code review of pre-installed applications to identify and remediate use-after-free patterns, focusing on proper pointer lifecycle management and memory deallocation handling.

Recommended fix Moderate confidence

OpenHarmony 5.0.3 or later stable release

  1. Check current OpenHarmony version using system settings or version query commands
  2. Verify the exact version number matches the affected range (>= 4.1.0, <= 5.0.2)
  3. Update to the latest available OpenHarmony release (version 5.0.3 or later) using official update mechanisms
  4. After update, verify the new version is no longer within the affected range
  5. Restart the device to ensure all patched components are fully loaded
Caveat Review release notes for any breaking changes between 5.0.2 and the target upgrade version before deploying in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openharmony Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24301 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24301 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data