CVE-2024-43697
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.1.0 and prior versions allow a local attacker cause DOS through improper input.
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.1.0 and prior versions contain a local denial-of-service vulnerability where improper input handling allows a local attacker to cause the system to become unavailable.
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.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
- 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 if OpenHarmony is installedCheck system information or OS version - look for 'OpenHarmony' or 'OpenAtom' in system details, or check /etc/os-release if accessibleAffected if The system is running OpenHarmony as the operating system
-
Determine the installed OpenHarmony versionRun 'getprop ro.build.version.harmony' or check /system/etc/param/ohos.para for version informationAffected if The version is 4.1.0 or any prior version (lower than 4.1.0)
-
Identify input-handling components or servicesList running services related to input handling - check for input, inputflinger, or input service processes using 'hisysevent' or service list commandsAffected if Input handling services are present and accessible to local users
-
Check for DoS indicators in system logsReview system logs (dmesg, logcat, or /var/log) for crashes, hangs, or service failures that may indicate a successful DoS attackAffected if System has experienced unexplained denials of service or input handler crashes
-
Verify input handling configurationExamine input configuration files in /system/etc/ or /data/param/ for any custom input processing settingsAffected if Non-default input handling configurations are present that may expose the vulnerability
A user is affected if they are running OpenHarmony version 4.1.0 or any prior version, with input handling services exposed to local attackers.
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 patches or updates provided by OpenHarmony for v4.1.0 and prior versions. Implement proper input validation and bounds checking to prevent DoS conditions from improper input.
- 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-2024-43697 — 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-43697 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