178 matches found
CVE-2020-35587
In Solstice Pod before 3.0.3, the firmware can easily be decompiled/disassembled. The decompiled/disassembled files contain non-obfuscated code. NOTE: it is unclear whether lack of obfuscation is directly associated with a negative impact, or instead only facilitates an attack technique...
CVE-2020-35587
In Solstice Pod before 3.0.3, the firmware can easily be decompiled/disassembled. The decompiled/disassembled files contain non-obfuscated code. NOTE: it is unclear whether lack of obfuscation is directly associated with a negative impact, or instead only facilitates an attack technique...
CVE-2020-35586
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...
CVE-2020-35584
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. An attacker suitably positioned to view a legitimate user's network traffic could record and monitor their interactions with the web services and obtain any...
CVE-2020-35586
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...
CVE-2020-35584
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. An attacker suitably positioned to view a legitimate user's network traffic could record and monitor their interactions with the web services and obtain any...
CVE-2020-35585
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...
CVE-2020-35585
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...
Design/Logic Flaw
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. An attacker suitably positioned to view a legitimate user's network traffic could record and monitor their interactions with the web services and obtain any...
Design/Logic Flaw
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...
Design/Logic Flaw
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...
CVE-2020-35586
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...
CVE-2020-35586
Solstice Pod (before 3.3.0) and Solstice Open4.3 vulnerability where the Administrator password can be enumerated by brute-forcing the Open Control API endpoint /Config/service/initModel?password= due to no password complexity requirements. Affected products are Solstice Pod prior to 3.3.0 and So...
CVE-2020-35585
CVE-2020-35585 affects Solstice Pod before 3.3.0 (or Open4.3). A brute‑force enumeration flaw enables guessing the screen key via the /lookin/info Solstice Open Control API, with only ~1.7 million possibilities. This is the vulnerability described in the CVE; the connected documents confirm the A...
CVE-2020-35585
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...
CVE-2020-35584
The vulnerability affects Solstice Pod prior to version 3.0.3. The web services expose a Browser Look‑in feature that allows connections over unencrypted channels. An attacker positioned to observe legitimate user network traffic could monitor interactions with the web services and capture sensit...
CVE-2020-35584
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. An attacker suitably positioned to view a legitimate user's network traffic could record and monitor their interactions with the web services and obtain any...
PT-2020-17354 · Mersive · Solstice Pod
Name of the Vulnerable Software and Affected Versions: Solstice Pod versions prior to 3.0.3 Description: The firmware of the affected versions can be easily decompiled or disassembled, and the resulting files contain non-obfuscated code. It is unclear whether the lack of obfuscation directly caus...
Mersive Solstice Pod Security Vulnerability
Mersive Solstice Pod is a software application for conference screen sharing from Mersive USA. A security vulnerability exists in versions prior to Solstice Pod 3.0.3, which stems from firmware that can be easily decompiled and disassembled. The decompiled disassembly file contains non-ambiguous...
Mersive Solstice Pod Authorization Issues Vulnerability
Mersive Solstice Pod is a software application for conference screen sharing from Mersive USA. A security vulnerability exists in Solstice Pod before 3.0.3 that originates when web services allow users to connect to them over an unencrypted channel via the browser view feature. An attacker who is...