dbcve.org
OpenharmonyOperating system · Openatom

CVE-2024-10074

HIGH · 7.8 CVSS v3.1 Published 2024-12-03
Fix available
A fix is available. Upgrade to after 4.1.1 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 v4.1.1 and prior versions allow a local attacker cause the common permission is upgraded to root through use after free.

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

OpenHarmony v4.1.1 and prior versions contain a use-after-free vulnerability that allows a local attacker to escalate common user permissions to root privileges. The vulnerability stems from improper memory management where memory is accessed after being freed, potentially enabling arbitrary code execution with elevated privileges.

MitigationApply the vendor patch when available; until then, restrict local access to trusted users only and monitor for suspicious privilege escalation attempts.

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.1

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 'getprop ro.build.version.harmonyos' or check system properties/config files that contain the HarmonyOS version string
    Affected if Returned version is 4.1.1 or any version lower than 4.1.1 (e.g., 4.1.0, 4.0.0, 3.x)
  2. Confirm product is OpenHarmony
    Verify the operating system is OpenHarmony by checking for harmony-specific system files, boot animations, or running 'getprop ro.build.display.id' to see if it references HarmonyOS or OpenHarmony
    Affected if System is confirmed to be an OpenHarmony-based product
  3. Check if vulnerability is patched
    Review vendor security advisories or check system update history for any CVE-2024-10074 related patches; look for patch dates after the CVE disclosure
    Affected if No specific patch for CVE-2024-10074 has been applied and version is <= 4.1.1

The environment is affected if it runs OpenHarmony version 4.1.1 or any prior version, as the use-after-free flaw enables local privilege escalation from standard user to root.

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 4.1.1
Interim mitigation

Apply the vendor patch when available; until then, restrict local access to trusted users only and monitor for suspicious privilege escalation attempts.

Fix this in Openharmony Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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