NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
78 matching advisories · page 3 of 3Index updated 14 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2020-28953 In BigBlueButton before 2.2.29, a user can vote more than once in a single poll. bigbluebutton · bigbluebutton 2020-11-19 medium6.1 CVE-2020-27642 A cross-site scripting (XSS) vulnerability exists in the 'merge account' functionality in admins.js in BigBlueButton Greenlight 2.7.6. bigbluebutton · greenlight 2020-10-22 high8.4 CVE-2020-27613 The installation procedure in BigBlueButton before 2.2.28 (or earlier) uses ClueCon as the FreeSWITCH password, which allows local users to achieve unintended … bigbluebutton · bigbluebutton 2020-10-21 medium4.3 CVE-2020-27612 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 informat… bigbluebutton · bigbluebutton 2020-10-21 high7.3 CVE-2020-27611 BigBlueButton through 2.2.28 uses STUN/TURN resources from a third party, which may represent an unintended endpoint. bigbluebutton · bigbluebutton 2020-10-21 high7.5 CVE-2020-27610 The installation procedure in BigBlueButton before 2.2.28 (or earlier) exposes certain network services to external interfaces, and does not automatically set … bigbluebutton · bigbluebutton 2020-10-21 medium5.3 CVE-2020-27609 BigBlueButton through 2.2.28 records a video meeting despite the deactivation of video recording in the user interface. bigbluebutton · bigbluebutton 2020-10-21 medium6.1 CVE-2020-27608 In BigBlueButton before 2.2.28 (or earlier), uploaded presentations are sent to clients without a Content-Type header, which allows XSS, as demonstrated by a .… bigbluebutton · bigbluebutton 2020-10-21 medium6.5 CVE-2020-27607 In BigBlueButton before 2.2.28 (or earlier), the client-side Mute button only signifies that the server should stop accepting audio data from the client. bigbluebutton · bigbluebutton 2020-10-21 medium5.3 CVE-2020-27606 BigBlueButton before 2.2.28 (or earlier) does not set the secure flag for the session cookie in an https session, which makes it easier for remote attackers to… bigbluebutton · bigbluebutton 2020-10-21 critical9.8 CVE-2020-27605 BigBlueButton through 2.2.28 uses Ghostscript for processing of uploaded EPS documents, and consequently may be subject to attacks related to a "schwache Sandb… bigbluebutton · bigbluebutton 2020-10-21 medium6.5 CVE-2020-27604 BigBlueButton before 2.3 does not implement LibreOffice sandboxing. bigbluebutton · bigbluebutton 2020-10-21 high7.5 CVE-2020-27603 BigBlueButton before 2.2.27 has an unsafe JODConverter setting in which LibreOffice document conversions can access external files. bigbluebutton · bigbluebutton 2020-10-21 medium6.5 CVE-2020-25820 BigBlueButton before 2.2.7 allows remote authenticated users to read local files and conduct SSRF attacks via an uploaded Office document that has a crafted UR… bigbluebutton · bigbluebutton 2020-10-21 high8.8 CVE-2020-26163 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… bigbluebutton · greenlight 2020-09-30 critical9.8 CVE-2020-12443 BigBlueButton before 2.2.6 allows remote attackers to read arbitrary files because the presfilename (lowercase) value can be a .pdf filename while the presFile… bigbluebutton · bigbluebutton 2020-04-29 medium6.1 CVE-2020-12113 BigBlueButton before 2.2.4 allows XSS via closed captions because dangerouslySetInnerHTML in React is used. bigbluebutton · bigbluebutton 2020-04-23 high7.5 CVE-2020-12112 BigBlueButton before 2.2.5 allows remote attackers to obtain sensitive files via Local File Inclusion. bigbluebutton · bigbluebutton 2020-04-23

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.