Alexandre Torres

The issue is related to a NULL pointer dereference in the telnetd application, which can occur via specific byte sequences, such as 0xff 0xf7 or 0xff 0xf8. In a typical installation, the telnetd application would crash, but the telnet service would remain available through inetd. However, if the telnetd application experiences many crashes within a short time interval, the telnet service would become unavailable after inetd logs a "telnet/tcp server failing (looping), service terminated" error.

The issue is a remote code execution vulnerability. A malicious attacker with access to the immediate subnet may potentially exploit this vulnerability, leading to information disclosure and a possible elevation of privileges.

The issue is related to a lack of input data sanitization in the Yealink Device Management platform, allowing a remote attacker to execute arbitrary commands as the root user. Specifically, the "/sm/api/v1/firewall/zone/services" API endpoint is vulnerable to command injection without requiring authentication.

An issue was discovered on V-SOL V1600D devices, where the string `K0LTdi@gnos312$` is compared to the password provided by the remote attacker. If it matches, access is provided.

An issue was discovered in V-SOL OLT devices, allowing the elevation of privilege of a CLI user to full administrative access by using a specific password for the enable command. The password `!j@l#y$z%x6x7q8c9z)` can be used to gain full administrative access.

An issue was discovered in V-SOL OLT devices, where command injection can occur via a crafted filename in the CLI, specifically in the "upload tftp syslog" and "upload tftp configuration" commands.

An issue was discovered in V-SOL OLT devices, where there is a hardcoded password `!j@l#y$z%x6x7q8c9z)` for the admin account to authenticate to the TELNET service.

An issue was discovered on V-SOL OLT devices, where a hardcoded RSA private key is contained in the firmware images. This key is specific to the V1600D4L and V1600D-MINI devices.

An issue was discovered in V-SOL OLT devices, where a low-privileged (non-admin) attacker can use a hardcoded password to create an admin user. The hardcoded password is 4ef9cea10b2362f15ba4558b1d5c081f.

An issue was discovered in V-SOL OLT devices where a hardcoded RSA private key is contained in the firmware images. This key is specific to V1600D, V1600G1, and V1600G2 devices.

An issue was discovered on V-SOL OLT devices. During the process of updating the firmware, the update script starts a telnetd -l /bin/sh process that does not require authentication for TELNET access.

An issue was discovered in the V-SOL OLT devices where TELNET is offered by default, but SSH is not always available. This allows an attacker to intercept passwords sent in cleartext and conduct a man-in-the-middle attack on the management of the appliance.

Name of the Vulnerable Software and Affected Versions: TOTOLINK A850R-V1 versions 1.0.1-B20150707.1612 and earlier TOTOLINK F1-V2 versions 1.1-B20150708.1646 and earlier Description: An issue allows the web management interface to be opened on the WAN interface by sending a specific `hel,xasf` packet. Recommendations: For TOTOLINK A850R-V1 versions 1.0.1-B20150707.1612 and earlier, restrict access to the WAN interface to prevent exploitation. For TOTOLINK F1-V2 versions 1.1-B20150708.1646 and earlier, consider disabling the web management interface on the WAN interface until a fix is available.

Name of the Vulnerable Software and Affected Versions: TOTOLINK A850R-V1 versions 1.0.1-B20150707.1612 and earlier TOTOLINK F1-V2 versions 1.1-B20150708.1646 and earlier Description: An issue was discovered in the management interface of the affected devices, allowing Remote Code Execution via the `sysCmd` parameter in the `formSysCmd` interface. Recommendations: For TOTOLINK A850R-V1 versions 1.0.1-B20150707.1612 and earlier, consider disabling the `formSysCmd` interface until a patch is available. For TOTOLINK F1-V2 versions 1.1-B20150708.1646 and earlier, restrict access to the management interface to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

The issue concerns a hardcoded ECDSA SSH key for the root account, located within the /opt/axess chroot directory tree.

The issue concerns a hardcoded DSA SSH key for the root account, located within the /opt/axess chroot directory tree.

The issue concerns a hardcoded RSA SSH key for the root account, which poses a security risk.

The issue concerns a hardcoded ECDSA SSH key for the root account, which poses a security risk.

The issue concerns a hardcoded DSA SSH key for the root account, which could potentially allow unauthorized access.

The issue concerns the presence of a hardcoded password, specifically the `axzyxel` password, for the `livedbuser` account.