CVE-2022-41962 json
BigBlueButton contains Incorrect Authorization for setting emoji status
published 3y ago modified 4mo ago also EUVD-2022-45068
- cvss
- 2.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
BigBlueButton is an open source web conferencing system. Versions prior to 2.4-rc-6, and 2.5-alpha-1 contain Incorrect Authorization for setting emoji status. A user with moderator rights can use the clear status feature to set any emoji status for other users. Moderators should only be able to set none as the status of other users. This issue is patched in 2.4-rc-6 and 2.5-alpha-1There are no workarounds.
Patch / fix
- bigbluebutton bigbluebutton 2.4
Is CVE-2022-41962 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.71% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N |
| NVD | 3.1 | 2.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N |
Affected products
- bigbluebutton bigbluebutton
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
github.com
/bigbluebutton/bigbluebutton/security/advisories/GHSA-88qf-33qm-9mm7
patch, release-notes, third-party-advisory
-
github.com
/bigbluebutton/bigbluebutton/releases/tag/v2.4-rc-6
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-41962
- NVD CVE-2022-41962
Fencer Intel 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.