dbcve.org
OpenharmonyOperating system · Openatom

CVE-2025-27248

MEDIUM · 5.5 CVSS v3.1 Published 2025-05-06
Fix available
A fix is available. Upgrade to after 5.0.3 or later.
See remediation →
57/100
Remediation priority · Elevated
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.3 and prior versions allow a local attacker case DOS through NULL pointer dereference.

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

In OpenHarmony v5.0.3 and prior versions, a local attacker can trigger a denial of service condition through NULL pointer dereference, likely due to missing null validation in a specific code path that fails to check pointer validity before dereferencing.

MitigationUpgrade to a version newer than v5.0.3 when available, or apply vendor-supplied security patches; if no patch exists, conduct source code review to identify locations lacking proper null pointer validation and add defensive null checks.

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:<= 5.0.3

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 'cat /etc/os-version' or access system settings to determine the exact installed OpenHarmony version number
    Affected if Version displays 5.0.3 or any version prior to 5.0.3
  2. Verify build fingerprint
    Execute 'getprop ro.build.version.sdk' or 'cat /proc/version' to confirm the OpenHarmony build information
    Affected if Build shows version 5.0.3 or lower
  3. Check system patch level
    Review the system security patch date in settings or via 'getprop ro.build.version.security_patch'
    Affected if Security patch level is dated before the fix for CVE-2025-27248 or shows no fix applied
  4. Monitor for NULL dereference crashes
    Examine system logs (via 'logcat' or journalctl) for crash reports containing 'NULL' or 'null pointer' errors in applications using the vulnerable component
    Affected if Logs show NULL pointer dereference errors occurring in the affected code path

A system is affected if it runs OpenHarmony version 5.0.3 or prior and has not had a security update addressing the NULL pointer dereference vulnerability.

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.

From vendor data
Upgrade available Upgrade to a release after 5.0.3
Interim mitigation

Upgrade to a version newer than v5.0.3 when available, or apply vendor-supplied security patches; if no patch exists, conduct source code review to identify locations lacking proper null pointer validation and add defensive null checks.

Fix this in Openharmony Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27248 — 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-27248 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