NetSight

Security Dashboard

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

Reset
141 matching advisories · page 4 of 5Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2021-35502 app/View/Elements/genericElements/IndexTable/Fields/generic_field.ctp in MISP 2.4.144 does not sanitize certain data related to generic-template:index. misp-project · misp 2021-06-25 high7.5 CVE-2021-31780 In app/Model/MispObject.php in MISP 2.4.141, an incorrect sharing group association could lead to information disclosure on an event edit. misp-project · misp 2021-04-23 medium5.5 CVE-2021-27904 An issue was discovered in app/Model/SharingGroupServer.php in MISP 2.4.139. misp-project · misp 2021-03-02 medium6.1 CVE-2020-24085 A cross-site scripting (XSS) vulnerability exists in MISP v2.4.128 in app/Controller/UserSettingsController.php at SetHomePage() function. misp-project · misp 2021-01-26 medium6.1 CVE-2021-3184 MISP 2.4.136 has XSS via a crafted URL to the app/View/Elements/global_menu.ctp user homepage favourite button. misp-project · misp 2021-01-19 medium6.1 CVE-2021-25325 MISP 2.4.136 has XSS via galaxy cluster element values to app/View/GalaxyElements/ajax/index.ctp. misp-project · misp 2021-01-19 medium6.1 CVE-2021-25324 MISP 2.4.136 has Stored XSS in the galaxy cluster view via a cluster name to app/View/GalaxyClusters/view.ctp. misp-project · misp 2021-01-19 critical9.1 CVE-2021-25323 The default setting of MISP 2.4.136 did not enable the requirements (aka require_password_confirmation) to provide the previous password when changing a passwo… misp-project · misp 2021-01-19 medium6.1 CVE-2020-29572 app/View/Elements/genericElements/SingleViews/Fields/genericField.ctp in MISP 2.4.135 has XSS via the authkey comment field. misp-project · misp 2020-12-06 critical9.8 CVE-2020-29006 MISP before 2.4.135 lacks an ACL check, related to app/Controller/GalaxyElementsController.php and app/Model/GalaxyElement.php. misp-project · misp 2020-11-24 medium6.1 CVE-2020-28947 In MISP 2.4.134, XSS exists in the template element index view because the id parameter is mishandled. misp-project · misp 2020-11-19 high7.5 CVE-2020-28043 MISP through 2.4.133 allows SSRF in the REST client via the use_full_path parameter with an arbitrary URL. misp-project · misp 2020-11-02 high7.5 CVE-2020-25766 An issue was discovered in MISP before 2.4.132. misp-project · misp 2020-09-18 high8.8 CVE-2020-15711 In MISP before 2.4.129, setting a favourite homepage was not CSRF protected. misp-project · misp 2020-07-14 medium4.3 CVE-2020-15412 An issue was discovered in MISP 2.4.128. misp-project · misp 2020-06-30 critical9.8 CVE-2020-15411 An issue was discovered in MISP 2.4.128. misp-project · misp 2020-06-30 high7.5 CVE-2020-14969 app/Model/Attribute.php in MISP 2.4.127 lacks an ACL lookup on attribute correlations. misp-project · misp 2020-06-22 medium6.1 CVE-2020-13153 app/View/Events/resolved_attributes.ctp in MISP before 2.4.126 has XSS in the resolved attributes view. misp-project · misp 2020-05-18 medium4.9 CVE-2020-11458 app/Model/feed.php in MISP before 2.4.124 allows administrators to choose arbitrary files that should be ingested by MISP. misp-project · misp 2020-04-02 medium6.1 CVE-2020-10247 MISP 2.4.122 has Persistent XSS in the sighting popover tool. misp-project · misp 2020-03-09 medium6.1 CVE-2020-10246 MISP 2.4.122 has reflected XSS via unsanitized URL parameters. misp-project · misp 2020-03-09 medium6.5 CVE-2020-8894 An issue was discovered in MISP before 2.4.121. misp-project · misp 2020-02-12 high7.5 CVE-2020-8893 An issue was discovered in MISP before 2.4.121. misp-project · misp 2020-02-12 high8.1 CVE-2020-8892 An issue was discovered in MISP before 2.4.121. misp-project · misp 2020-02-12 medium5.9 CVE-2020-8891 An issue was discovered in MISP before 2.4.121. misp-project · misp 2020-02-12 medium5.9 CVE-2020-8890 An issue was discovered in MISP before 2.4.121. misp-project · misp 2020-02-12 medium5.3 CVE-2019-19379 In app/Controller/TagsController.php in MISP 2.4.118, users can bypass intended restrictions on tagging data. misp-project · misp 2019-11-28 medium6.5 CVE-2019-16202 MISP before 2.4.115 allows privilege escalation in certain situations. misp-project · misp 2019-09-10 medium6.1 CVE-2019-14286 In app/webroot/js/event-graph.js in MISP 2.4.111, a stored XSS vulnerability exists in the event-graph view when a user toggles the event graph view. misp-project · misp 2019-07-27 high7.2 CVE-2019-12868 app/Model/Server.php in MISP 2.4.109 allows remote command execution by a super administrator because the PHP file_exists function is used with user-controlled… misp-project · misp 2019-06-18

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.