Leo Lin

A denial-of-service issue exists in the WebSocket API caused by insufficient validation and handling of JSON-based requests. A low-privileged authenticated attacker can send a specially crafted request to the WebSocket API, leading to service disruption and potentially causing an unexpected device reboot.

Improper ownership management allows a low-privileged authenticated user to access a configuration file containing the hashed password of the administrative account. This can lead to the disclosure of sensitive information. Exploitation is only possible if the configuration file has been exported. This issue does not affect the integrity or availability of the product or subsequent systems.

Improper validation of length parameters in the HTTPS management interface allows an unauthenticated remote attacker to send specially crafted requests. This triggers a buffer overflow, a condition where a program writes more data to a block of memory than it can hold, causing the web service to become unresponsive. Successful exploitation results in a denial-of-service condition that requires a device reboot to restore normal operation. This issue impacts device availability, but does not affect confidentiality or integrity.

An unauthenticated device registration issue exists due to Improperly Controlled Modification of Dynamically-Determined Object Attributes. An attacker can exploit this by sending a crafted JSON payload to the `/api/v1/devices/register` endpoint, enabling registration of unauthorized devices without authentication. The vulnerability allows for limited data modification, but does not impact the confidentiality or availability of the device or subsequent systems. The vulnerable parameter is the JSON payload sent to the API endpoint.