NetSight

Security Dashboard

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

Reset
49 matching advisories · page 2 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2021-30478 An issue was discovered in Zulip Server before 3.4. zulip · zulip_server 2021-04-15 medium4.3 CVE-2021-30477 An issue was discovered in Zulip Server before 3.4. zulip · zulip_server 2021-04-15 medium5.3 CVE-2020-10858 Zulip Desktop before 5.0.0 allows attackers to perform recording via the webcam and microphone due to a missing permission request handler. zulip · zulip_desktop 2021-02-05 medium6.1 CVE-2020-24582 Zulip Desktop before 5.4.3 allows XSS because string escaping is mishandled during composition of the HTML for the user interface. zulipchat · zulip_desktop 2020-09-10 medium5.4 CVE-2020-14194 Zulip Server before 2.1.5 allows reverse tabnapping via a topic header link. zulip · zulip_server 2020-08-21 medium6.1 CVE-2020-12759 Zulip Server before 2.1.5 allows reflected XSS via the Dropbox webhook. zulip · zulip_server 2020-08-21 medium6.1 CVE-2020-9445 Zulip Server before 2.1.3 allows XSS via the modal_link feature in the Markdown functionality. zulip · zulip_server 2020-04-20 medium6.1 CVE-2020-9444 Zulip Server before 2.1.3 allows reverse tabnabbing via the Markdown functionality. zulip · zulip_server 2020-04-20 medium5.4 CVE-2020-10935 Zulip Server before 2.1.3 allows XSS via a Markdown link, with resultant account takeover. zulip · zulip_server 2020-04-20 medium6.1 CVE-2020-9443 Zulip Desktop before 4.0.3 loaded untrusted content in an Electron webview with web security disabled, which can be exploited for XSS in a number of ways. zulipchat · zulip_desktop 2020-03-18 medium6.1 CVE-2019-19775 The image thumbnailing handler in Zulip Server versions 1.9.0 to before 2.0.8 allowed an open redirect that was visible to logged-in users. zulip · zulip_server 2019-12-18 medium5.4 CVE-2019-16216 Zulip server before 2.0.5 incompletely validated the MIME types of uploaded files. zulip · zulip_server 2019-09-18 medium6.5 CVE-2019-16215 The Markdown parser in Zulip server before 2.0.5 used a regular expression vulnerable to exponential backtracking. zulip · zulip_server 2019-09-18 medium5.4 CVE-2018-9999 In Zulip Server versions before 1.7.2, there was an XSS issue with user uploads and the (default) LOCAL_UPLOADS_DIR storage backend. zulip · zulip_server 2018-04-18 medium6.1 CVE-2018-9990 In Zulip Server versions before 1.7.2, there was an XSS issue with stream names in topic typeahead. zulip · zulip_server 2018-04-18 medium6.1 CVE-2018-9987 In Zulip Server versions 1.5.x, 1.6.x, and 1.7.x before 1.7.2, there was an XSS issue with muting notifications. zulip · zulip_server 2018-04-18 medium6.1 CVE-2018-9986 In Zulip Server versions before 1.7.2, there were XSS issues with the frontend markdown processor. zulip · zulip_server 2018-04-18 medium6.5 CVE-2017-0896 Zulip Server 1.5.1 and below suffer from an error in the implementation of the invite_by_admins_only setting in the Zulip group chat application server that al… zulip · zulip_server 2017-06-02 medium4.3 CVE-2017-0881 An error in the implementation of an autosubscribe feature in the check_stream_exists route of the Zulip group chat application server before 1.4.3 allowed an … zulip · zulip_server 2017-03-28

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.