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.
AI analysis not yet available
Plain-English explanation, risk summary, and remediation steps will appear here once AI analysis is complete.
No Fix Known
No patch has been released yet. Apply workarounds or mitigations where available.
| Vendor | Product | Versions | Fixed In |
|---|---|---|---|
| getnexx | nxal-100_firmware | nxal100v-p1-9-1 | - |
| getnexx | nxg-100b_firmware | nxg100bv-p3-4-1 | - |
| getnexx | nxpg-100w_firmware |
Published
CVE disclosed publicly
Last Modified
Most recent update
Indexed to CVEInsight
Added to this platform
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4
Affected Products
2
References
getnexx / nxal-100_firmware
| nxpg100cv4-0-0 |
| - |
| getnexx | nxg-200_firmware | nxg200v-p3-4-1 | - |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Exploitability
Impact