dbcve.org
Command InjectionWeakness · CWE-77

CVE-2023-5878

CRITICAL · 9.4 CVSS v4.0 Published 2025-02-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
Honeywell OneWireless Wireless Device Manager (WDM) for the following versions R310.x, R320.x, R321.x, R322.1, R322.2, R323.x, R330.1 contains a command injection vulnerability. An attacker who is authenticated could use the firmware update process to potentially exploit the vulnerability, leading to a command injection. Honeywell recommends updating to R322.3, R330.2 or the most recent version of this product2.

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 · high confidence

Command injection vulnerability in Honeywell OneWireless Wireless Device Manager (WDM) firmware update process. An authenticated attacker can inject arbitrary commands during the firmware update, leading to complete system compromise.

MitigationUpdate WDM firmware to version R322.3, R330.2, or the latest version to remediate the command injection vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Network
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 installed
    Locate the WDM installation directory, typically at /opt/honeywell/wdm, or query system inventory for Honeywell OneWireless Wireless Device Manager
    Affected if Product is present on the system
  2. Check installed WDM firmware version
    Access WDM administrative web interface and navigate to System > Firmware or run version command via dmcli, or inspect version file in /opt/honeywell/wdm/version
    Affected if Version is below R322.3 or R330.2 (any version prior to the fixed releases)
  3. Verify firmware update functionality is accessible
    Check WDM configuration files (wdm.properties or wdm.xml in config directory) for firmware update feature settings, or verify the firmware upload endpoint is enabled in the web interface
    Affected if Firmware update feature is enabled and version is vulnerable
  4. Confirm authentication is required for firmware update
    Review access control settings in WDM configuration or verify that firmware update requires authenticated session via web interface or API
    Affected if Unauthenticated access to firmware update is possible and version is vulnerable

User is affected if Honeywell OneWireless WDM is installed with a version prior to R322.3 or R330.2 and the firmware update feature is accessible to an authenticated attacker

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

Update WDM firmware to version R322.3, R330.2, or the latest version to remediate the command injection vulnerability.

Recommended fix High confidence

R322.3, R330.2, or most recent version

  1. Identify the current firmware version of the Honeywell OneWireless Wireless Device Manager (WDM) by accessing the device management interface
  2. Download the firmware update from the official Honeywell support portal at process.honeywell.com or authorized distribution channels
  3. Review the firmware release notes to ensure compatibility with your specific WDM hardware model
  4. Follow the standard firmware upgrade procedure documented in the Honeywell OneWireless WDM installation and operation guide
  5. Initiate the firmware update process through the WDM management interface or appropriate update mechanism
  6. Verify successful installation by confirming the new firmware version matches R322.3, R330.2, or the latest available version
  7. Validate that the WDM device and associated wireless network operations are functioning normally after the update

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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