dbcve.org
OpenharmonyOperating system · Openatom

CVE-2023-47857

MEDIUM · 5.5 CVSS v3.1 Published 2024-01-02
Fix available
A fix is available. Upgrade to after 3.2.2 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
in OpenHarmony v3.2.2 and prior versions allow a local attacker cause multimedia camera crash through modify a released pointer.

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

This is a use-after-free vulnerability in OpenHarmony's multimedia camera subsystem. A local attacker can cause a camera crash by modifying a memory pointer after it has been released, leading to a denial of service condition. The attack requires local access to the device.

MitigationUpdate OpenHarmony to a version beyond v3.2.2 that includes the patch for this vulnerability. If immediate patching is not possible, restrict physical and local access to the device to prevent exploitation.

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

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 OpenHarmony version
    Check the system version by examining the /etc/version or /system/build.prop file, or use the 'getprop' command if available on the device
    Affected if The version displayed is 3.2.2 or any version lower than 3.2.2
  2. Verify camera subsystem is present
    Check for camera-related system services or camera daemon processes running on the device, such as camera_service or similar multimedia processes
    Affected if The camera subsystem is installed and running on the device
  3. Confirm local access exposure
    Evaluate whether physical access or local shell access to the device is possible or has been granted to untrusted users
    Affected if Local or physical access to the device is available to unauthorized users

A device is affected if it runs OpenHarmony version 3.2.2 or lower AND has the camera subsystem enabled, with exposure to local attackers.

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

Update OpenHarmony to a version beyond v3.2.2 that includes the patch for this vulnerability. If immediate patching is not possible, restrict physical and local access to the device to prevent exploitation.

Fix this in Openharmony Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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