NetSight

Security Dashboard

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

Reset
1,300 matching advisories · page 17 of 44Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2024-3856 A use-after-free could occur during WASM execution if garbage collection ran during the creation of an array. mozilla · firefox 2024-04-16 high8.8 CVE-2024-3854 In some code patterns the JIT incorrectly optimized switch statements and generated code with out-of-bounds-reads. mozilla · firefox, mozilla · thunderbird 2024-04-16 high7.5 CVE-2024-3853 A use-after-free could result if a JavaScript realm was in the process of being initialized when a garbage collection started. mozilla · firefox 2024-04-16 high7.5 CVE-2024-3852 GetBoundName could return the wrong version of an object when JIT optimizations were applied. mozilla · firefox, mozilla · thunderbird 2024-04-16 high7.7 CVE-2024-30263 macro-pdfviewer is a PDF Viewer Macro for XWiki using Mozilla pdf.js. 2024-04-04 high7.5 CVE-2024-31392 If an insecure element was added to a page after a delay, Firefox would not replace the secure icon with a mixed content security status This vulnerability aff… mozilla · firefox 2024-04-03 high8.4 CVE-2024-29944 An attacker was able to inject an event handler into a privileged object that would allow arbitrary JavaScript execution in the parent process. mozilla · firefox, debian · debian_linux 2024-03-22 high8.8 CVE-2024-2614 Memory safety bugs present in Firefox 123, Firefox ESR 115.8, and Thunderbird 115.8. mozilla · firefox, mozilla · thunderbird, debian · debian_linux 2024-03-19 high7.5 CVE-2024-2613 Data was not properly sanitized when decoding a QUIC ACK frame; this could have led to unrestricted memory consumption and a crash. mozilla · firefox 2024-03-19 high8.1 CVE-2024-2612 If an attacker could find a way to trigger a particular code path in `SafeRefPtr`, it could have triggered a crash or potentially be leveraged to achieve code … mozilla · firefox, mozilla · thunderbird 2024-03-19 high8.4 CVE-2024-2608 `AppendEncodedAttributeValue(), ExtraSpaceNeededForAttrEncoding()` and `AppendEncodedCharacters()` could have experienced integer overflows, causing underalloc… mozilla · firefox, mozilla · thunderbird, debian · debian_linux 2024-03-19 high8.1 CVE-2024-2607 Return registers were overwritten which could have allowed an attacker to execute arbitrary code. mozilla · firefox, mozilla · thunderbird, debian · debian_linux 2024-03-19 high7.5 CVE-2024-1936 The encrypted subject of an email message could be incorrectly and permanently assigned to an arbitrary other email message in Thunderbird's local cache. mozilla · thunderbird, debian · debian_linux 2024-03-04 high7.8 CVE-2024-26283 An attacker could have executed unauthorized scripts on top origin sites using a JavaScript URI when opening an external URL with a custom Firefox scheme. mozilla · firefox 2024-02-22 high7.1 CVE-2024-26282 Using an AMP url with a canonical element, an attacker could have executed JavaScript from an opened bookmarked page. mozilla · firefox 2024-02-22 high8.1 CVE-2024-1563 An attacker could have executed unauthorized scripts on top origin sites using a JavaScript URI when opening an external URL with a custom Firefox scheme and a… mozilla · firefox_focus 2024-02-22 high8.1 CVE-2024-1557 Memory safety bugs present in Firefox 122. mozilla · firefox 2024-02-20 high8.3 CVE-2024-1555 When opening a website using the `firefox://` protocol handler, SameSite cookies were not properly respected. mozilla · firefox 2024-02-20 high8.1 CVE-2024-1553 Memory safety bugs present in Firefox 122, Firefox ESR 115.7, and Thunderbird 115.7. mozilla · firefox, mozilla · thunderbird, debian · debian_linux 2024-02-20 high7.5 CVE-2024-1552 Incorrect code generation could have led to unexpected numeric conversions and potential undefined behavior.*Note:* This issue only affects 32-bit ARM devices. mozilla · firefox, mozilla · thunderbird, debian · debian_linux 2024-02-20 high7.5 CVE-2024-1546 When storing and re-accessing data on a networking channel, the length of buffers may have been confused, resulting in an out-of-bounds memory read. mozilla · firefox, mozilla · thunderbird, debian · debian_linux 2024-02-20 high8.8 CVE-2024-0755 Memory safety bugs present in Firefox 121, Firefox ESR 115.6, and Thunderbird 115.6. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird +1 2024-01-23 high8.8 CVE-2024-0751 A malicious devtools extension could have been used to escalate privileges. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird +1 2024-01-23 high8.8 CVE-2024-0750 A bug in popup notifications delay calculation could have made it possible for an attacker to trick a user into granting permissions. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird +1 2024-01-23 high8.8 CVE-2024-0745 The WebAudio `OscillatorNode` object was susceptible to a stack buffer overflow. mozilla · firefox 2024-01-23 high7.5 CVE-2024-0744 In some circumstances, JIT compiled code could have dereferenced a wild pointer value. mozilla · firefox 2024-01-23 high7.5 CVE-2024-0743 An unchecked return value in TLS handshake code could have caused a potentially exploitable crash. mozilla · firefox 2024-01-23 high7.5 CVE-2024-0605 Using a javascript: URI with a setTimeout race condition, an attacker can execute unauthorized scripts on top origin sites in urlbar. mozilla · firefox_focus 2024-01-22 high8.8 CVE-2023-6873 Memory safety bugs present in Firefox 120. mozilla · firefox, debian · debian_linux 2023-12-19 high8.8 CVE-2023-6866 TypedArrays can be fallible and lacked proper exception handling. mozilla · firefox 2023-12-19

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.