CVE-2024-37077
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 remote attacker arbitrary code execution in pre-installed apps through out-of-bounds write.
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 v4.0.0 and prior versions contain an out-of-bounds write vulnerability in pre-installed applications that can be exploited by a remote attacker to achieve arbitrary code execution. The vulnerability stems from improper bounds checking when writing to memory, allowing an attacker to overwrite adjacent memory locations and hijack control flow.
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.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify OpenHarmony installationCheck system information or boot logs for OpenHarmony OS identity. On embedded devices, inspect /proc/version, system properties, or boot messages for 'OpenHarmony' or 'Openatom' strings.Affected if The system runs OpenHarmony as its operating system.
-
Determine OpenHarmony versionRetrieve the installed OpenHarmony version from system settings, version files, or command-line tools such as 'getprop' on Android-like builds, or by examining /etc/version or /usr/lib/version information.Affected if The installed version is 4.0.0 or any version prior to 4.0.0.
-
Locate pre-installed applicationsExamine the application directory for pre-installed apps. Common locations include /system/app, /preinstall, or /vendor/preinstall on OpenHarmony-based devices. List installed packages using system package managers or application management tools.Affected if Pre-installed applications exist on the device and are actively used.
-
Assess network exposureReview network configuration and firewall rules to determine if the device is directly accessible from untrusted networks. Check listening ports and services bound to external interfaces.Affected if The device or its pre-installed applications are exposed to untrusted network paths without adequate network segmentation or filtering.
A user is affected if their device runs OpenHarmony version 4.0.0 or prior, has pre-installed applications present, and those applications or the device itself are reachable from untrusted networks.
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 security patches from OpenHarmony project as soon as available; until then, minimize network exposure of affected devices and consider network segmentation for IoT/embedded devices running OpenHarmony.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37077 — 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-37077 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