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

CVE-2022-4240

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable 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
Missing Authentication for Critical Function vulnerability in Honeywell OneWireless allows Authentication Bypass. This issue affects OneWireless version 322.1

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

Missing Authentication for Critical Function vulnerability in Honeywell OneWireless version 322.1 allows unauthenticated remote attackers to bypass authentication and access critical functions without credentials.

MitigationApply vendor patch or upgrade from OneWireless 322.1 to a patched version; if unavailable, implement network segmentation and restrict access to the affected component via firewall rules.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 the Honeywell OneWireless device
    Locate the Honeywell Onewireless Network Wireless Device Manager in your environment and note its network identity
    Affected if The device is a Honeywell Onewireless Network Wireless Device Manager
  2. Determine the firmware version
    Access the device management interface or use SNMP/CLI to query the firmware version. Common commands include checking system info via the web UI or using 'show version' via console/SSH
    Affected if The firmware version is r322.1 or any version lower than r322.2 (for example, r322.0, r321.x, etc.)
  3. Verify the management interface exposure
    Check network accessibility of the device web management interface or API endpoints from untrusted networks. Review firewall rules and network segmentation around the device
    Affected if The device management interface is reachable from networks outside the trusted internal network
  4. Confirm authentication is not enforced
    Attempt to access critical device functions without providing credentials. Observe if the system grants access to administrative operations without authentication
    Affected if Critical functions are accessible without any authentication credentials being required

Your environment is affected if you have a Honeywell Onewireless Network Wireless Device Manager running firmware version r322.1 or any version below r322.2, and the management interface is accessible to network 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch or upgrade from OneWireless 322.1 to a patched version; if unavailable, implement network segmentation and restrict access to the affected component via firewall rules.

Recommended fix High confidence

r322.2 (or any version >= r322.2)

  1. Verify current firmware version on the OneWireless Network Wireless Device Manager is 322.1 (affected version)
  2. Obtain the r322.2 firmware update from the official Honeywell process.honeywell.com support portal or trusted distribution channel
  3. Review Honeywell OneWireless upgrade documentation for any specific prerequisites or backup procedures
  4. Apply the firmware upgrade following the manufacturer's recommended procedure (typically via web UI, console, or dedicated management tool)
  5. After upgrade, verify the device is running firmware version r322.2 or later
  6. Confirm the vulnerability is remediated by verifying authentication is now required for the previously affected function
Caveat Review release notes for r322.2 to check for any functional changes or compatibility considerations with connected field devices

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
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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