CVE-2025-20063
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 · uneditedin OpenHarmony v5.0.3 and prior versions allow a local attacker cause apps crash through type confusion.
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 confidenceOpenHarmony v5.0.3 and prior versions contain a type confusion vulnerability that allows a local attacker to cause applications to crash. The vulnerability stems from improper type handling in the operating system that can be exploited by manipulating object types at runtime, leading to a denial-of-service condition.
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<= 5.0.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify OpenHarmony installationCheck system information or package manager for OpenHarmony version. On development systems, run 'hdc shell getprop ro.build.version.sdk' or check /system/etc/param/oh-para.conf for version markers.Affected if OpenHarmony is installed and version is 5.0.3 or lower
-
Verify OpenHarmony versionRun 'hdc shell getprop' to retrieve ro.build.version.release or ro.build.display.id. Compare the version number to the affected range.Affected if Version is 5.0.3 or any prior version (v5.0.x <= 5.0.3, v4.x, v3.x)
-
Assess local access exposureDetermine if untrusted local users or processes can interact with the device or execute code. Check for multi-user access, debug interfaces, or shell access enabled on the system.Affected if Local untrusted users or processes have access to the device or can invoke runtime object operations
-
Monitor for application crashesReview system logs (logcat or /data/log/) for abnormal application termination events. Look for crash dumps or ANR (Application Not Responding) reports occurring without clear cause.Affected if Applications crash unexpectedly with type confusion or memory corruption signatures in crash logs
-
Check for anomalous runtime behaviorUse debugging or tracing tools to observe object type transitions at runtime. Look for unexpected type handling in application logs or debugging output.Affected if Object type manipulation is possible through application interfaces or debugging features
A user is affected if OpenHarmony version 5.0.3 or lower is installed AND local attackers can manipulate object types to trigger application crashes.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor patch for OpenHarmony v5.0.3 when available. Until then, limit local device access and monitor for anomalous application behavior that could indicate exploitation attempts.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20063 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-20063 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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