This page aggregates publicly disclosed CVE and security risk information related to getnexx, with CVSS, EPSS, publication dates, and vulnerability intelligence data to help assess potential risk and remediation priority.
| CVE | 概要 | ソース | CVSS 最大値 | EPSS（%） | 公開 | 更新 |
|---|---|---|---|---|---|---|
| CVE-2023-1752 | The listed versions of Nexx Smart Home devices could allow any user to register an already registered alarm or associated device with only the device’s MAC address. | [email protected] | 8.1 | 0.52% | 2023-04-04 | 2026-06-17 |
| CVE-2023-1751 | 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. | [email protected] | 7.5 | 0.59% | 2023-04-04 | 2026-06-17 |
| CVE-2023-1750 | The listed versions of Nexx Smart Home devices lack proper access control when executing actions. An attacker with a valid NexxHome deviceId could retrieve device history, set device settings, and retrieve device information. | [email protected] | 7.1 | 0.48% | 2023-04-04 | 2026-06-17 |
| CVE-2023-1749 | The listed versions of Nexx Smart Home devices lack proper access control when executing actions. An attacker with a valid NexxHome deviceId could send API requests that the affected devices would execute. | [email protected] | 6.5 | 0.50% | 2023-04-04 | 2026-06-17 |
| CVE-2023-1748 | The listed versions of Nexx Smart Home devices use hard-coded credentials. An attacker with unauthenticated access to the Nexx Home mobile application or the affected firmware could view the credentials and access the MQ Telemetry Server (MQTT) server and the ability to remotely control garage doors or smart plugs for any customer. | [email protected] | 9.3 | 0.83% | 2023-04-04 | 2026-06-17 |