Skybridge Mb-a110 Firmware vulnerabilities
6 known vulnerabilities in Skybridge Mb-a110 Firmware from Seiko-sol. 6 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 9.8 Critical severity
SkyBridge MB-A100/MB-A110: Improper Neutralization of Special Elements used in an OS Command
Improper neutralization of special elements used in a command ('Command Injection') exists in SkyBridge MB-A100/MB-A110 firmware Ver. 4.2.2 and earlier and SkyBridge BASIC MB-A130 firmware Ver. 1.5.5 and earlier. If the remote monitoring and control function i
- 7.5 High severity
SkyBridge MB-A100/110: Weak Password Requirements
Use of weak credentials exists in SkyBridge MB-A100/110 firmware Ver. 4.2.0 and earlier, which may allow a remote unauthenticated attacker to decrypt password for the WebUI of the product.
- 7.5 High severity
SkyBridge MB-A100/110: Missing Authentication for Critical Functionality
Missing authentication for critical function exists in SkyBridge MB-A100/110 firmware Ver. 4.2.0 and earlier, which may allow a remote unauthenticated attacker to execute some critical functions without authentication, e.g., rebooting the product.
- 9.8 Critical severity
Skybridge Mb-a100 Firmware: Use of Hard-coded Credentials
Seiko SkyBridge MB-A100/A110 v4.2.0 and below implements a hard-coded passcode for the root account. Attackers are able to access the passcord via the file /etc/ciel.cfg.
- 9.8 Critical severity
Skybridge Mb-a100 Firmware: Unrestricted Upload of File with Dangerous Type
Seiko SkyBridge MB-A100/A110 v4.2.0 and below was discovered to contain an arbitrary file upload vulnerability via the restore backup function. This vulnerability allows attackers to execute arbitrary code via a crafted html file.
- 9.8 Critical severity
Skybridge Mb-a100 Firmware: Improper Neutralization of Special Elements used in a Command
Seiko SkyBridge MB-A100/A110 v4.2.0 and below was discovered to contain a command injection vulnerability via the ipAddress parameter at 07system08execute_ping_01.