# CVE-2021-22155: Auth bypass in n/a

> An authentication bypass in the SAML component allows attackers to gain unauthorized access to user accounts on BlackBerry Workspaces Server.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-h557-xrrh-37xw

## What is CVE-2021-22155?

CVE-2021-22155 is a high-severity authentication bypass vulnerability in n/a, published on 12 May 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Authentication Bypass vulnerability in the SAML Authentication component of BlackBerry Workspaces Server (deployed with Appliance-X) version(s) 10.1, 9.1 and earlier could allow an attacker to potentially gain access to the application in the context of the targeted user’s account.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2021-22155?

It affects 1 product.


Products: Blackberry Workspaces Server.

## How do I fix CVE-2021-22155?

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

## Is CVE-2021-22155 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-11652](https://insights.sbomify.com/CVE-2020-11652/): SaltStack Salt Path Traversal (medium 6.5, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22155 and fix it if it is affected.

What it is: CVE-2021-22155 is a high-severity authentication bypass vulnerability in n/a, published on 12 May 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22155 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-2021-22155/ (Markdown: https://insights.sbomify.com/CVE-2021-22155/index.md)
```

## Sources

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

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