CVE-2022-41960 json
BigBlueButton contains DoS via failed authToken validation
published 2022-12-15 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-45066
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- bigbluebutton bigbluebutton 2.4.3
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
Affected products
- bigbluebutton bigbluebutton
Classification
- Weakness
-
- CWE-345 Insufficient Verification of Data Authenticity
References
-
github.com
/bigbluebutton/bigbluebutton/security/advisories/GHSA-rgjp-3r74-g4cm
release-notes, third-party-advisory
-
github.com
/bigbluebutton/bigbluebutton/releases/tag/v2.4.3
release-notes, third-party-advisory
-
github.com
/bigbluebutton/bigbluebutton/releases/tag/v2.5-alpha-1
release-notes, third-party-advisory
Sources
- CVE List CVE-2022-41960
- NVD CVE-2022-41960
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.