# CVE-2022-1805: Security feature bypass in Tera2 Zero Client

> Attackers can bypass certificate verification in Amazon Workspaces connections from PCoIP Zero Clients via Man-in-the-Middle attacks.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-mqfh-36p4-43qx

## What is CVE-2022-1805?

CVE-2022-1805 is a high-severity vulnerability in Tera2 Zero Client, published on 28 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When connecting to Amazon Workspaces, the SHA256 presented by AWS connection provisioner is not fully verified by Zero Clients. The issue could be exploited by an adversary that places a MITM (Man in the Middle) between a zero client and AWS session provisioner in the network. This issue is only applicable when connecting to an Amazon Workspace from a PCoIP Zero Client.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2022-1805?

It affects 1 product.


Products: Teradici Tera2 Pcoip Zero Client Firmware.

## How do I fix CVE-2022-1805?

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

## Is CVE-2022-1805 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1805 and fix it if it is affected.

What it is: CVE-2022-1805 is a high-severity vulnerability in Tera2 Zero Client, published on 28 Jul 2022. 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-2022-1805 in the wild and no public exploit code.

Affected product: Tera2 Zero Client. 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-2022-1805/ (Markdown: https://insights.sbomify.com/CVE-2022-1805/index.md)
```

## Sources

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

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