CVE-2022-29232 json
Exposure of messages in BigBlueButton public chats
published 2022-06-01 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-33592
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
BigBlueButton is an open source web conferencing system. Starting with version 2.2 and prior to versions 2.3.9 and 2.4-beta-1, an attacker can circumvent access controls to obtain the content of public chat messages from different meetings on the server. The attacker must be a participant in a meeting on the server. BigBlueButton versions 2.3.9 and 2.4-beta-1 contain a patch for this issue. There are currently no known workarounds.
Patch / fix
- bigbluebutton bigbluebutton 2.3.9
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
1.08% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Affected products
- bigbluebutton bigbluebutton
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
github.com
/bigbluebutton/bigbluebutton/pull/12861
patch, third-party-advisory
-
github.com
/bigbluebutton/bigbluebutton/security/advisories/GHSA-3fqh-p4qr-vfm9
patch, third-party-advisory
-
github.com
/bigbluebutton/bigbluebutton/releases/tag/v2.3.9
release-notes, third-party-advisory
-
github.com
/bigbluebutton/bigbluebutton/releases/tag/v2.4-beta-1
release-notes, third-party-advisory
Sources
- CVE List CVE-2022-29232
- NVD CVE-2022-29232
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.