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

CVE-2022-43485

MEDIUM · 6.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 →
71/100
Remediation priority · Elevated
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
Use of Insufficiently Random Values in Honeywell OneWireless. This vulnerability may allow attacker to manipulate claims in client's JWT token. 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

The vulnerability involves insufficient randomness in the JWT token generation mechanism in Honeywell OneWireless version 322.1. Weak random values used during token creation could allow an attacker to predict or brute-force valid tokens, enabling manipulation of JWT claims such as user identity, permissions, or session data.

MitigationUpgrade OneWireless to a version beyond 322.1 that implements cryptographically secure random number generation for JWT token signing. If upgrading is not immediately possible, implement additional validation layers and monitor for suspicious token manipulation attempts.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 OneWireless Wireless Device Manager firmware version
    Access the device management interface (web UI or CLI) and locate the firmware version information, typically found under System Info, Device Status, or About sections
    Affected if The displayed firmware version is before r322.2 (e.g., 322.1, 322.0, or earlier)
  2. Confirm JWT token generation is in use
    Check if the device is configured to issue or validate JWT tokens for authentication or session management - look for OAuth, token-based auth, or API security settings in the management interface
    Affected if JWT token generation is enabled and the firmware version is below r322.2
  3. Review token signing configuration if accessible
    If accessible via CLI or config files, examine the JWT signing configuration to verify the random number generation method being used
    Affected if Weak or non-cryptographic randomness is configured for token signing and firmware is prior to r322.2

You are affected if your Honeywell OneWireless Wireless Device Manager firmware version is below r322.2 and the device uses JWT token-based authentication.

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 to a version beyond 322.1 that implements cryptographically secure random number generation for JWT token signing. If upgrading is not immediately possible, implement additional validation layers and monitor for suspicious token manipulation attempts.

Recommended fix High confidence

r322.2 or later

  1. 1. Identify the OneWireless Network Wireless Device Manager device(s) running firmware version 322.1 or earlier
  2. 2. Obtain the fixed firmware version r322.2 or later from Honeywell's official support portal (process.honeywell.com)
  3. 3. Review Honeywell's official firmware upgrade documentation for OneWireless devices
  4. 4. Apply the firmware upgrade following Honeywell's documented upgrade procedure
  5. 5. After upgrade, verify the device is running firmware version r322.2 or later
  6. 6. Confirm that JWT token generation now uses sufficient randomness by testing authentication functionality
Caveat Firmware upgrades carry inherent risk; ensure backups and downtime windows are planned per Honeywell's upgrade guidelines

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
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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-43485 — 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-43485 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