Vulnerabilities > Mersive
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2020-12-23 | CVE-2020-35587 | Unspecified vulnerability in Mersive Solstice Firmware In Solstice Pod before 3.0.3, the firmware can easily be decompiled/disassembled. | 7.5 |
| 2020-12-23 | CVE-2020-35586 | Improper Restriction of Excessive Authentication Attempts vulnerability in Mersive Solstice POD Firmware In Solstice Pod before 3.3.0 (or Open4.3), the Administrator password can be enumerated using brute-force attacks via the /Config/service/initModel?password= Solstice Open Control API because there is no complexity requirement (e.g., it might be all digits or all lowercase letters). | 7.5 |
| 2020-12-23 | CVE-2020-35585 | Improper Restriction of Excessive Authentication Attempts vulnerability in Mersive Solstice POD Firmware In Solstice Pod before 3.3.0 (or Open4.3), the screen key can be enumerated using brute-force attacks via the /lookin/info Solstice Open Control API because there are only 1.7 million possibilities. | 7.5 |
| 2020-12-23 | CVE-2020-35584 | Cleartext Transmission of Sensitive Information vulnerability in Mersive Solstice POD Firmware In Solstice Pod before 3.0.3, the web services allow users to connect to them over unencrypted channels via the Browser Look-in feature. | 5.9 |
| 2020-11-11 | CVE-2020-27523 | Use of Externally-Controlled Format String vulnerability in Mersive Solstice POD Firmware Solstice-Pod up to 5.0.2 WEBRTC server mishandles the format-string specifiers %x; %p; %c and %s in the screen_key, display_name, browser_name, and operation_system parameter during the authentication process. | 7.5 |
| 2019-11-27 | CVE-2017-12945 | OS Command Injection vulnerability in Mersive Solstice Firmware Insufficient validation of user-supplied input for the Solstice Pod before 2.8.4 networking configuration enables authenticated attackers to execute arbitrary commands as root. | 8.8 |