Parul Sindhwad

The issue is related to an insufficient session expiration, which could allow an attacker to transmit passwords over unencrypted connections, resulting in the product becoming vulnerable to interception. This could permit attackers to intercept passwords.

The issue concerns the transmission of user credentials in clear text without encryption when a user is added or user credentials are changed via the device's webpage. This affects the security of user credentials.

The issue concerns the transmission of credentials using a weak encoding method, specifically base64. An attacker present in the network can intercept the traffic and decode the credentials.

The issue exists due to insufficient validation of user-supplied input for the `SMTP Password` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, potentially allowing them to perform stored XSS attacks on the targeted system.

The issue exists due to insufficient validation of user-supplied input for the `L2TP/PPTP Username` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, potentially allowing them to perform stored XSS attacks on the targeted system.

The issue exists due to insufficient validation of user-supplied input for the `Preshared Phrase` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, potentially allowing stored XSS attacks on the targeted system.

This issue exists due to insufficient validation of user-supplied input for the `Network Name (SSID)` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue exists due to insufficient validation of user-supplied input for the `Device Name` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue exists due to the transmission of authentication credentials in plaintext over the network. A remote attacker could exploit this by eavesdropping on the victim’s network traffic to extract the `username` and `password` from the web interface (Login Page) of the targeted system.

This issue exists due to the transmission of authentication credentials in plaintext over the network. A remote attacker could exploit this by eavesdropping on the victim’s network traffic to extract the `username` and `password` from the web interface, specifically the Password Reset Page, of the targeted system.

This issue is due to insufficient validation of user-supplied input for the `Add Downstream Frequency` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, potentially allowing a Denial of Service (DoS) attack on the targeted system.

This issue is due to insufficient validation of user-supplied input for the `Set Upstream Channel ID (UCID)` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, potentially allowing them to perform a Denial of Service (DoS) attack on the targeted system.

This issue is due to insufficient validation of user-supplied input for the `Traceroute` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue exists due to insufficient validation of user-supplied input for the `Time Server 1` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

The issue exists due to insufficient validation of user-supplied input for the `Time Server 2` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue exists due to insufficient validation of user-supplied input for the `Time Server 3` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue is due to insufficient validation of user-supplied input for the `Description` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue exists due to insufficient validation of user-supplied input for the `URL` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue exists due to insufficient validation of user-supplied input for the `Contact Email Address` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue is due to insufficient validation of user-supplied input for the `SMTP Server Name` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.