Vulnerability Description
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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Mersive | Solstice Pod Firmware | < 3.3.0 |
| Mersive | Solstice Pod | - |
Related Weaknesses (CWE)
References
- https://documentation.mersive.com/content/pages/release-notes.htmRelease NotesVendor Advisory
- https://github.com/aress31/solstice-pod-cvesExploitThird Party Advisory
- https://www.mersive.com/uk/products/solstice/ProductVendor Advisory
- https://documentation.mersive.com/content/pages/release-notes.htmRelease NotesVendor Advisory
- https://github.com/aress31/solstice-pod-cvesExploitThird Party Advisory
- https://www.mersive.com/uk/products/solstice/ProductVendor Advisory
FAQ
What is CVE-2020-35585?
CVE-2020-35585 is a vulnerability with a CVSS score of 7.5 (HIGH). 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.
How severe is CVE-2020-35585?
CVE-2020-35585 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2020-35585?
Check the references section above for vendor advisories and patch information. Affected products include: Mersive Solstice Pod Firmware, Mersive Solstice Pod.