dbcve.org
OpenharmonyApplication

CVE-2022-38700

HIGH · 8.8 CVSS v3.1 Published 2022-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges 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
OpenHarmony-v3.1.1 and prior versions have a permission bypass vulnerability. LAN attackers can bypass permission control and get control of camera service.

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 v3.1.1 and prior versions contain a permission bypass vulnerability in the camera service that allows LAN attackers to circumvent permission controls and gain unauthorized control of the device camera.

MitigationApply any available OpenHarmony security updates that address this vulnerability, and implement network segmentation to limit LAN attack surface for affected devices.

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
OpenharmonyApplication
Affected:= 3.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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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 checks

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

  1. Identify OpenHarmony version
    Check the system settings or version information menu on the device, or run 'getprop ro.build.version.release' or 'cat /proc/version' via ADB if available
    Affected if The version is 3.1.1 or earlier (any version <= 3.1.1)
  2. Verify camera service is active
    Check running processes for camera-related services using 'ps -A | grep -i camera' or check camera app is installed and the camera framework is present on the system
    Affected if Camera service daemon or camera framework components are present and running on the device
  3. Confirm network exposure of camera service
    Check if camera service ports are listening on network interfaces (e.g., using 'netstat -an' or checking /proc/net/tcp) or verify if camera functionality is exposed via any network API
    Affected if The camera service or its APIs are accessible over network interfaces rather than solely through local IPC
  4. Check camera permission enforcement
    Review camera service configuration files in /etc/ or /data/ for permission settings, or observe if camera access is granted without proper user consent prompts
    Affected if Camera permissions can be bypassed or are not properly enforced when accessed from LAN sources

The device is affected if it runs OpenHarmony version 3.1.1 or earlier AND has the camera service enabled with network accessibility that allows LAN-based requests to bypass permission checks.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply any available OpenHarmony security updates that address this vulnerability, and implement network segmentation to limit LAN attack surface for affected devices.

Recommended fix Moderate confidence

OpenHarmony v3.1.2 or later (consult official OpenHarmony security advisories for exact fixed release)

  1. 1. Identify all devices running OpenHarmony v3.1.1 or prior versions in the environment
  2. 2. Check the OpenHarmony release notes or security advisories for the fixed version containing the camera service permission bypass fix
  3. 3. Plan the upgrade procedure for each affected device, ensuring backup of critical data
  4. 4. Execute the upgrade to the fixed version (v3.1.2 or later) following OpenHarmony's standard upgrade documentation
  5. 5. Verify the camera service operates correctly after upgrade and confirm the permission bypass vulnerability is resolved
  6. 6. Review access controls and network segmentation to limit LAN attack surface as an additional mitigation layer
Caveat Review release notes for any breaking changes between v3.1.1 and the target fixed version before upgrading

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

Fix this in Openharmony Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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