CVE-2025-22837
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.2 and prior versions allow a local attacker cause 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 confidenceOpenHarmony v5.0.2 and prior versions contain a NULL pointer dereference vulnerability that can be exploited by a local attacker to cause a denial of service. The vulnerability allows a local attacker to trigger a NULL pointer dereference condition leading to a system crash or service disruption.
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>= 4.1.0, <= 5.0.2CVSS 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 installationLocate OpenHarmony on the system by checking system information, build files, or package metadata. Common locations include system partitions, build configuration files, or version declaration files within the OpenHarmony directory structure.Affected if OpenHarmony is present on the system
-
Determine installed OpenHarmony versionRetrieve the version number of the installed OpenHarmony instance. This can typically be found in system build properties, version files, or by querying the system through appropriate diagnostic commands or configuration files that declare the OS version.Affected if A specific version number cannot be determined or the system reports no version information
-
Compare version against affected rangeCompare the installed version to the affected range: >= 4.1.0 and <= 5.0.2. Check if the version falls within or overlaps with this range.Affected if The installed version is 4.1.0, 4.1.1, 4.2.0, 4.3.0, 5.0.0, 5.0.1, 5.0.2, or any version between 4.1.0 and 5.0.2 inclusive
The environment is affected if OpenHarmony is installed and its version falls within the range of 4.1.0 through 5.0.2 inclusive, as this version range contains the NULL pointer dereference vulnerability.
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 CVE-2025-22837 when available, or implement proper NULL pointer validation checks in the affected code paths to prevent dereferencing uninitialized or null pointers.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22837 — 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-22837 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