dbcve.org
OpenharmonyOperating system · Openatom

CVE-2023-0083

MEDIUM · 5.5 CVSS v3.1 Published 2023-03-10
Fix available
A fix is available. Upgrade to after 3.1.5 or later.
See remediation →
57/100
Remediation priority · Elevated
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
The ArKUI framework subsystem within OpenHarmony-v3.1.5 and prior versions, OpenHarmony-v3.0.7 and prior versions has an Improper Input Validation vulnerability which local attackers can exploit this vulnerability to send malicious data, causing the current application to crash.

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

The ArKUI framework in OpenHarmony versions 3.1.5 and prior, and 3.0.7 and prior, contains an improper input validation vulnerability. Local attackers can send malicious data to the framework, causing the current application to crash due to the lack of proper input validation checks.

MitigationOrganizations using affected OpenHarmony versions should update to patched versions once released. Until then, limit local application access and monitor for application crash patterns.

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:>= 3.0, <= 3.0.7>= 3.1, <= 3.1.5

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the OpenHarmony version
    Check the system or application build information for the OpenHarmony version number (typically found in system settings, build metadata, or about/framework info)
    Affected if The version is 3.0.x where x <= 7, or 3.1.x where x <= 5
  2. Confirm ArKUI framework usage
    Review the application codebase or framework dependencies to determine if the ArKUI (formerly called Ace) UI framework is included and actively used
    Affected if The application uses the ArKUI framework for UI rendering
  3. Verify input handling paths
    Inspect the application's data handling code to identify if ArKUI components accept and process external or user-supplied input (such as intent extras, file data, or IPC messages)
    Affected if ArKUI-based components process unsanitized external input without validation checks
  4. Check for crash monitoring
    Review system or application logs for unexpected crash reports, especially those originating from ArKUI framework components
    Affected if Recent or recurring crashes are logged from ArKUI-related processes after receiving external data

A system is affected if it runs OpenHarmony version 3.0.7 or earlier, or 3.1.5 or earlier, and applications using the ArKUI framework accept external input that could be exploited locally.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.1.5
Interim mitigation

Organizations using affected OpenHarmony versions should update to patched versions once released. Until then, limit local application access and monitor for application crash patterns.

Recommended fix Moderate confidence

OpenHarmony 3.0.8+ or 3.1.6+ (or latest stable 3.x release)

  1. Identify the current OpenHarmony version in use (check build.gradle or version metadata)
  2. If version is 3.0.x, upgrade to version 3.0.8 or later (preferably the latest 3.0.x stable release)
  3. If version is 3.1.x, upgrade to version 3.1.6 or later (preferably the latest 3.1.x stable release)
  4. If version is 3.2.x or later, verify the version includes the ArKUI framework fix for CVE-2023-0083
  5. After upgrade, rebuild and test the application to ensure ArKUI components function correctly
Caveat Review OpenHarmony release notes between affected and target version for any breaking API changes in ArKUI framework

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openharmony Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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