# CVE-2020-35585: Auth bypass in n/a

> Attackers can brute-force the screen key via the Open Control API due to low entropy, bypassing authentication on Solstice Pods.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w6cg-v47q-5p36

## What is CVE-2020-35585?

CVE-2020-35585 is a high-severity authentication bypass vulnerability in n/a, published on 23 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2020-35585?

It affects 1 product.


Products: Mersive Solstice Pod Firmware.

## How do I fix CVE-2020-35585?

No fix has been published for CVE-2020-35585 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-35585 being exploited?

There is no known exploitation of CVE-2020-35585 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-35586](https://insights.sbomify.com/CVE-2020-35586/): Auth bypass in n/a (high 7.5)
- [CVE-2020-27523](https://insights.sbomify.com/CVE-2020-27523/): Denial of service in n/a (high 7.5)
- [CVE-2025-66573](https://insights.sbomify.com/CVE-2025-66573/): Solstice Pod API Session Key Extraction via API Endpoint (medium 6.9)
- [CVE-2020-35584](https://insights.sbomify.com/CVE-2020-35584/): Information disclosure in n/a (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-35585 and fix it if it is affected.

What it is: CVE-2020-35585 is a high-severity authentication bypass vulnerability in n/a, published on 23 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-35585 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-35585/ (Markdown: https://insights.sbomify.com/CVE-2020-35585/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-35585
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-35585
- OSV: https://osv.dev/vulnerability/CVE-2020-35585

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-35585/
Summaries are generated and may contain mistakes; the official description above is the record.