dbcve.org
Nxal 100 FirmwareOperating system · Getnexx

CVE-2023-1751

MEDIUM · 5.3 CVSS v3.1 Published 2023-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
The listed versions of Nexx Smart Home devices use a WebSocket server that does not validate if the bearer token in the Authorization header belongs to the device attempting to associate. This could allow any authorized user to receive alarm information and signals meant for other devices which leak a deviceId.

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

Nexx Smart Home devices run a WebSocket server that fails to validate whether the bearer token in the Authorization header corresponds to the device attempting to associate. This authorization flaw allows any authenticated user to subscribe to alarm information and signals intended for other devices by leveraging a leaked deviceId, enabling cross-device information disclosure.

MitigationImplement binding validation between the bearer token and deviceId during WebSocket handshake to ensure only the legitimate device owner can receive that device's signals and alarm data.

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
Nxal 100 FirmwareOperating system
Affected:<= nxal100v-p1-9-1
Nxg 100b FirmwareOperating system
Affected:<= nxg100bv-p3-4-1
Nxpg 100w FirmwareOperating system
Affected:<= nxpg100cv4-0-0
Nxg 200 FirmwareOperating system
Affected:<= nxg200v-p3-4-1

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 device model and firmware version
    Access the device administration interface or check the device label to determine if the model is one of: Nxal 100, Nxg 100b, Nxpg 100w, or Nxg 200. Then check the firmware version through the device settings or by querying the device's system information endpoint.
    Affected if The device model is one of the affected models and the firmware version is at or below the listed versions (nxal100v-p1-9-1, nxg100bv-p3-4-1, nxpg100cv4-0-0, or nxg200v-p3-4-1).
  2. Verify WebSocket server is accessible
    Attempt to establish a WebSocket connection to the device using the standard WebSocket protocol (wss:// or ws://) on the port typically used by the device's web interface. Check if the WebSocket endpoint responds to connection requests.
    Affected if The WebSocket server is reachable and accepts connection attempts, indicating the service is active.
  3. Confirm WebSocket authentication mechanism
    Initiate a WebSocket handshake with a valid bearer token in the Authorization header but use a deviceId parameter value that differs from the device associated with that token. Observe whether the server accepts the connection.
    Affected if The server accepts the WebSocket connection and allows subscription to device data using a token that does not match the target deviceId, indicating the authorization binding is missing.
  4. Test cross-device data subscription
    With an authenticated session, obtain a valid bearer token for one device, then attempt to subscribe to alarms or signals from a different device using that same token but specifying a different deviceId. Verify if alarm data from the alternate device is received.
    Affected if The server returns alarm information or signals from a device other than the one associated with the bearer token, confirming the authorization bypass is present.

The device is affected if it is a Getnexx model (Nxal 100, Nxg 100b, Nxpg 100w, or Nxg 200) running firmware at or below the specified version limits and the WebSocket server permits subscription to a device using a bearer token that does not correspond to that device's deviceId.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement binding validation between the bearer token and deviceId during WebSocket handshake to ensure only the legitimate device owner can receive that device's signals and alarm data.

Fix this in Nxal 100 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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