CVE-2024-31078
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 v4.0.0 and prior versions allow a local attacker cause service crash 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 confidenceA local attacker with access to an OpenHarmony v4.0.0 or prior device can trigger a NULL pointer dereference vulnerability, causing the affected service to crash. This is a denial-of-service vulnerability that requires local access to the device.
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.0.1CVSS 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 boot logs for OpenHarmony version. On the device, look for version markers in /proc/version, system properties, or boot messages.Affected if The system is running OpenHarmony and the version is below 4.0.1
-
Determine exact version numberRun 'getprop' command (Android/鸿蒙 system property) or check /system/build.prop for 'ro.build.version.release' or 'ro.build.display.id' to obtain the precise version string.Affected if The displayed version is v4.0.0 or any version lower than 4.0.1
-
Verify the vulnerable service is presentCheck for the existence of the affected service binary or process. Since specific service name is not provided, identify any running native services that handle the affected code path.Affected if The service that contains the vulnerable code is present and running on the device
If the device runs OpenHarmony version 4.0.0 or any version prior to 4.0.1 and has the affected service active, it is vulnerable to this local DoS via NULL pointer dereference.
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.
dbcve · scoped4.0.1
Apply the vendor patch for OpenHarmony when available; until then, limit physical and local access to affected devices to reduce attack surface.
OpenHarmony 4.0.1
- 1. Identify all OpenHarmony instances currently running versions prior to 4.0.1
- 2. Plan an upgrade to OpenHarmony version 4.0.1 or later
- 3. Before upgrading, backup all critical data and configurations
- 4. Perform the upgrade following OpenHarmony's standard upgrade procedures
- 5. After upgrade, verify that services restart properly and the NULL pointer dereference vulnerability is resolved
- 6. Test that the system functions normally post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31078 — 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-2024-31078 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