NetSight

Security Dashboard

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

Reset
1,300 matching advisories · page 16 of 44Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2024-7528 Incorrect garbage collection interaction in IndexedDB could have led to a use-after-free. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2024-08-06 high8.8 CVE-2024-7527 Unexpected marking work at the start of sweeping could have led to a use-after-free. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2024-08-06 high8.1 CVE-2024-7525 It was possible for a web extension with minimal permissions to create a `StreamFilter` which could be used to read and modify the response body of requests on… mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2024-08-06 high8.1 CVE-2024-7523 A select option could partially obscure security prompts. mozilla · firefox_mobile 2024-08-06 high8.8 CVE-2024-7522 Editor code failed to check an attribute value. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2024-08-06 high8.8 CVE-2024-7521 Incomplete WebAssembly exception handing could have led to a use-after-free. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2024-08-06 high8.8 CVE-2024-7520 A type confusion bug in WebAssembly could be leveraged by an attacker to potentially achieve code execution. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2024-08-06 high8.8 CVE-2024-6615 Memory safety bugs present in Firefox 127 and Thunderbird 127. mozilla · firefox, mozilla · thunderbird 2024-07-09 high8.8 CVE-2024-6609 When almost out-of-memory an elliptic curve key which was never allocated could have been freed again. mozilla · firefox, mozilla · thunderbird 2024-07-09 high8.8 CVE-2024-6607 It was possible to prevent a user from exiting pointerlock when pressing escape and to overlay customValidity notifications from a `<select>` element ove… mozilla · firefox, mozilla · thunderbird 2024-07-09 high8.2 CVE-2024-6606 Clipboard code failed to check the index on an array access. mozilla · firefox, mozilla · thunderbird 2024-07-09 high8.8 CVE-2024-6605 Firefox Android allowed immediate interaction with permission prompts. mozilla · firefox 2024-07-09 high7.5 CVE-2024-6604 Memory safety bugs present in Firefox 127, Firefox ESR 115.12, and Thunderbird 115.12. mozilla · firefox, mozilla · thunderbird 2024-07-09 high7.4 CVE-2024-6603 In an out-of-memory scenario an allocation could fail but free would have been called on the pointer afterwards leading to memory corruption. mozilla · firefox, mozilla · thunderbird 2024-07-09 high7.5 CVE-2024-5702 Memory corruption in the networking stack could have led to a potentially exploitable crash. mozilla · firefox, mozilla · thunderbird 2024-06-11 high8.6 CVE-2024-5696 By manipulating the text in an `<input>` tag, an attacker could have caused corrupt memory leading to a potentially exploitable crash. mozilla · firefox, mozilla · thunderbird, debian · debian_linux 2024-06-11 high7.5 CVE-2024-5694 An attacker could have caused a use-after-free in the JavaScript engine to read memory in the JavaScript string section of the heap. mozilla · firefox 2024-06-11 high8.1 CVE-2024-5688 If a garbage collection was triggered at the right time, a use-after-free could have occurred during object transplant. mozilla · firefox, mozilla · thunderbird 2024-06-11 high7.0 CVE-2024-5700 Memory safety bugs present in Firefox 126, Firefox ESR 115.11, and Thunderbird 115.11. mozilla · firefox, mozilla · thunderbird, Mozilla · Firefox +2 2024-06-11 high8.8 CVE-2024-4777 Memory safety bugs present in Firefox 125, Firefox ESR 115.10, and Thunderbird 115.10. mozilla · firefox, mozilla · thunderbird, debian · debian_linux 2024-05-14 high8.2 CVE-2024-4776 A file dialog shown while in full-screen mode could have resulted in the window remaining disabled. mozilla · firefox 2024-05-14 high7.5 CVE-2024-4773 When a network error occurred during page load, the prior content could have remained in view with a blank URL bar. mozilla · firefox 2024-05-14 high8.6 CVE-2024-4771 A memory allocation check was missing which would lead to a use-after-free if the allocation failed. mozilla · firefox 2024-05-14 high8.8 CVE-2024-4770 When saving a page to PDF, certain font styles could have led to a potential use-after-free crash. mozilla · firefox, mozilla · thunderbird 2024-05-14 high8.1 CVE-2024-4765 Web application manifests were stored by using an insecure MD5 hash which allowed for a hash collision to overwrite another application's manifest. mozilla · firefox 2024-05-14 high8.8 CVE-2024-4367 PDF.js vulnerable to arbitrary JavaScript execution upon opening a malicious PDF npm · pdfjs-dist 2024-05-07 high8.1 CVE-2024-3865 Memory safety bugs present in Firefox 124. mozilla · firefox 2024-04-16 high8.1 CVE-2024-3864 Memory safety bug present in Firefox 124, Firefox ESR 115.9, and Thunderbird 115.9. mozilla · firefox, mozilla · thunderbird, debian · debian_linux 2024-04-16 high7.5 CVE-2024-3858 It was possible to mutate a JavaScript object so that the JIT could crash while tracing it. mozilla · firefox 2024-04-16 high7.8 CVE-2024-3857 The JIT created incorrect code for arguments in certain cases. mozilla · firefox, mozilla · thunderbird, debian · debian_linux 2024-04-16

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.