# CVE-2022-41960: BigBlueButton contains DoS via failed authToken validation

> An attacker can force a victim to leave a conference by exploiting insufficient authentication token validation in BigBlueButton.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **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:** 15 Dec 2022
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-rgjp-3r74-g4cm

## What is CVE-2022-41960?

CVE-2022-41960 is a medium-severity denial of service vulnerability in bigbluebutton, published on 15 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

BigBlueButton is an open source web conferencing system. Versions prior to 2.4.3, are subject to Insufficient Verification of Data Authenticity, resulting in Denial of Service. An attacker can make a Meteor call to `validateAuthToken` using a victim's userId, meetingId, and an invalid authToken. This forces the victim to leave the conference, because the resulting verification failure is also observed and handled by the victim's client. The attacker must be a participant in any meeting on the server. This issue is patched in version 2.4.3. There are no workarounds.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 1 product.


Products: Bigbluebutton Bigbluebutton.

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

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

## Is CVE-2022-41960 being exploited?

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

## Other vulnerabilities in bigbluebutton

- [CVE-2020-27602](https://insights.sbomify.com/CVE-2020-27602/): Other in n/a (critical 9.8)
- [CVE-2020-27605](https://insights.sbomify.com/CVE-2020-27605/): Code injection in n/a (critical 9.8)
- [CVE-2020-12443](https://insights.sbomify.com/CVE-2020-12443/): Path traversal in n/a (critical 9.8)
- [CVE-2020-27613](https://insights.sbomify.com/CVE-2020-27613/): Hardcoded credentials in n/a (high 8.4)
- [CVE-2021-4143](https://insights.sbomify.com/CVE-2021-4143/): Cross-site Scripting (XSS) - Generic in bigbluebutton/bigbluebutton (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-41960 is a medium-severity denial of service vulnerability in bigbluebutton, published on 15 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-41960 in the wild and no public exploit code.

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

## Sources

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

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