Vulnerabilities (CVE)

Filtered by vendor Bigbluebutton Subscribe
Total 47 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2020-27609 1 Bigbluebutton 1 Bigbluebutton 2020-10-29 5.0 MEDIUM 5.3 MEDIUM
BigBlueButton through 2.2.28 records a video meeting despite the deactivation of video recording in the user interface. This may result in data storage beyond what is authorized for a specific meeting topic or participant.
CVE-2020-27612 1 Bigbluebutton 1 Bigbluebutton 2020-10-29 4.0 MEDIUM 4.3 MEDIUM
Greenlight in BigBlueButton through 2.2.28 places usernames in room URLs, which may represent an unintended information leak to users in a room, or an information leak to outsiders if any user publishes a screenshot of a browser window.
CVE-2020-27613 1 Bigbluebutton 1 Bigbluebutton 2020-10-29 4.6 MEDIUM 8.4 HIGH
The installation procedure in BigBlueButton before 2.2.28 (or earlier) uses ClueCon as the FreeSWITCH password, which allows local users to achieve unintended FreeSWITCH access.
CVE-2020-27642 1 Bigbluebutton 1 Greenlight 2020-10-27 4.3 MEDIUM 6.1 MEDIUM
A cross-site scripting (XSS) vulnerability exists in the 'merge account' functionality in admins.js in BigBlueButton Greenlight 2.7.6.
CVE-2020-26163 1 Bigbluebutton 1 Greenlight 2020-10-15 6.8 MEDIUM 8.8 HIGH
BigBlueButton Greenlight before 2.5.6 allows HTTP header (Host and Origin) attacks, which can result in Account Takeover if a victim follows a spoofed password-reset link.
CVE-2020-12113 1 Bigbluebutton 1 Bigbluebutton 2020-09-30 4.3 MEDIUM 6.1 MEDIUM
BigBlueButton before 2.2.4 allows XSS via closed captions because dangerouslySetInnerHTML in React is used.
CVE-2020-12443 1 Bigbluebutton 1 Bigbluebutton 2020-05-06 7.5 HIGH 9.8 CRITICAL
BigBlueButton before 2.2.6 allows remote attackers to read arbitrary files because the presfilename (lowercase) value can be a .pdf filename while the presFilename (mixed case) value has a ../ sequence. This can be leveraged for privilege escalation via a directory traversal to bigbluebutton.properties. NOTE: this issue exists because of an ineffective mitigation to CVE-2020-12112 in which there was an attempted fix within an NGINX configuration file, without considering that the relevant part of NGINX is case-insensitive.