dbcve.org
OpenharmonyApplication

CVE-2022-42463

HIGH · 8.8 CVSS v3.1 Published 2022-10-14
Fix available
A fix is available. Upgrade to after 3.1.2 or later.
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.2 and prior versions have an authenication bypass vulnerability in a callback handler function of Softbus_server in communication subsystem. Attackers can launch attacks on distributed networks by sending Bluetooth rfcomm packets to any remote device and executing arbitrary commands.

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 versions v3.1.2 and prior contain an authentication bypass vulnerability in the Softbus_server component's callback handler within the communication subsystem. Attackers can exploit this by sending specially crafted Bluetooth rfcomm packets to remote devices on distributed networks, enabling execution of arbitrary commands.

MitigationApply any available OpenHarmony security updates addressing this vulnerability; if no patch exists, implement additional authentication and authorization controls in the Softbus_server callback handler before processing incoming rfcomm packets.

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, <= 3.1.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
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. Check OpenHarmony version
    Run `getprop ro.build.version.sdk` or check /etc/version to determine the installed OpenHarmony version. Compare it against the affected range: v3.1 through v3.1.2 inclusive.
    Affected if The installed version is v3.1, v3.1.1, or v3.1.2.
  2. Verify Softbus_server component presence
    Check if the Softbus_server process or service is running on the device. Look for processes containing 'softbus' or 'soft_bus' in the process list using `ps -A | grep -i softbus` or examine /etc/init/ for service configurations.
    Affected if The Softbus_server component is installed and running on the device.
  3. Confirm Bluetooth rfcomm is enabled
    Inspect the Bluetooth configuration or runtime settings to determine if rfcomm (Radio Frequency Communication) protocol support is enabled. Check for rfcomm-related kernel modules or configuration files under /etc/bluetooth/ or /system/etc/bluetooth/.
    Affected if Bluetooth rfcomm support is enabled in the Bluetooth stack.
  4. Assess network exposure
    Determine if the device has distributed network connectivity enabled, which allows communication with remote devices. Check network interfaces, firewall rules, or Softbus_server configuration for distributed network or cross-device communication settings.
    Affected if The device is connected to a distributed network or has enabled cross-device communication features accessible to other devices.

The environment is affected if the installed OpenHarmony version falls within v3.1 through v3.1.2, the Softbus_server component is active, Bluetooth rfcomm is enabled, and the device has distributed network connectivity that allows incoming Bluetooth rfcomm packets from remote devices.

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.2
Interim mitigation

Apply any available OpenHarmony security updates addressing this vulnerability; if no patch exists, implement additional authentication and authorization controls in the Softbus_server callback handler before processing incoming rfcomm packets.

Recommended fix Moderate confidence

OpenHarmony 3.2 or later LTS release

  1. 1. Identify the current OpenHarmony version in your environment by checking the version manifest or build configuration
  2. 2. Plan for upgrade to OpenHarmony 3.2 or later release, as versions 3.1.x (3.1, 3.1.1, 3.1.2) contain the authentication bypass vulnerability in Softbus_server
  3. 3. Before upgrading, review the Softbus_server component in the communication subsystem for any custom configurations that may need adjustment
  4. 4. Perform upgrade following standard OpenHarmony upgrade procedures
  5. 5. After upgrade, verify that the Bluetooth rfcomm callback handler in Softbus_server is functioning correctly and accepting only authenticated connections
Caveat Review release notes for 3.2.x for any API or component changes that may affect your application compatibility

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

Fix this in Openharmony Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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