dbcve.org
Onewireless Network Wireless Device Manager FirmwareOperating system · Honeywell

CVE-2022-46361

MEDIUM · 6.8 CVSS v3.1 Published 2023-05-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
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
An attacker having physical access to WDM can plug USB device to gain access and execute unwanted commands. A malicious user could enter a system command along with a backup configuration, which could result in the execution of unwanted commands. This issue affects OneWireless all versions up to 322.1 and fixed in version 322.2.

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 command injection vulnerability in Honeywell's OneWireless WDM (Wireless Device Manager). An attacker with physical access can exploit the backup configuration restore function by embedding malicious system commands within a backup configuration file. When the compromised backup is restored, arbitrary commands are executed with the privileges of the WDM system.

MitigationUpgrade OneWireless WDM to version 322.2 or later. Additionally, enforce strict physical access controls to the WDM hardware and implement USB device policies to prevent unauthorized device insertion.

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
Onewireless Network Wireless Device Manager FirmwareOperating system
Affected:< r322.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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/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. Confirm Honeywell OneWireless WDM is in use
    Identify the device model and confirm it is a Honeywell OneWireless Network Wireless Device Manager. Check the device label, management console, or network inventory for the device type.
    Affected if The device is a Honeywell OneWireless WDM unit.
  2. Check firmware version
    Access the WDM management interface or device console and retrieve the current firmware version. Compare it against the reported affected version r322.2.
    Affected if The installed firmware version is earlier than r322.2.
  3. Verify backup restore feature availability
    Check the WDM management interface or documentation to determine if the backup configuration restore function is enabled or accessible. This feature is typically found in the system administration or maintenance section.
    Affected if The backup configuration restore function is present and accessible on the device.
  4. Assess physical access controls
    Review physical security controls around the WDM hardware. Determine if unauthorized individuals could gain physical access to connect USB devices or manipulate backup files.
    Affected if Physical access to the WDM hardware is not restricted or monitored.

The environment is affected if the device is a Honeywell OneWireless WDM running firmware earlier than r322.2 and the backup configuration restore feature is accessible, especially if physical access controls are weak.

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

Upgrade OneWireless WDM to version 322.2 or later. Additionally, enforce strict physical access controls to the WDM hardware and implement USB device policies to prevent unauthorized device insertion.

Recommended fix High confidence

firmware version 322.2

  1. Obtain the fixed firmware version 322.2 from the official Honeywell process.honeywell.com portal or authorized distribution channel
  2. Access the OneWireless Wireless Device Manager (WDM) administrative interface
  3. Navigate to the firmware upgrade or system maintenance section
  4. Upload and apply firmware version 322.2 to the Wireless Device Manager
  5. Allow the device to complete the upgrade process and reboot
  6. Verify the upgrade was successful by checking the firmware version in the WDM interface
  7. Confirm that the USB port and backup configuration functionality no longer accept arbitrary command injection

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

Fix this in Onewireless Network Wireless Device Manager Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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