NetSight

Security Dashboard

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

Reset
1,623 matching advisories · page 13 of 55Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2023-4574 When creating a callback over IPC for showing the Color Picker window, multiple of the same callbacks could have been created at a time and eventually all simu… mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2023-09-11 medium5.5 CVE-2023-4104 An invalid Polkit Authentication check and missing authentication requirements for D-Bus methods allowed any local user to configure arbitrary VPN setups. mozilla · vpn 2023-09-11 medium6.5 CVE-2023-4573 When receiving rendering data over IPC `mStream` could have been destroyed when initialized, which could have led to a use-after-free causing a potentially exp… mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2023-09-11 medium5.5 CVE-2023-4054 When opening appref-ms files, Firefox did not warn the user that these files may contain malicious code. mozilla · firefox 2023-08-01 medium6.5 CVE-2023-4053 A website could have obscured the full screen notification by using a URL with a scheme handled by an external program, such as a mailto URL. mozilla · firefox 2023-08-01 medium6.5 CVE-2023-4052 The Firefox updater created a directory writable by non-privileged users. mozilla · firefox, mozilla · firefox_esr 2023-08-01 medium5.9 CVE-2023-4049 Race conditions in reference counting code were found through code inspection. mozilla · firefox, debian · debian_linux 2023-08-01 medium5.3 CVE-2023-4046 In some circumstances, a stale value could have been used for a global variable in WASM JIT analysis. mozilla · firefox, debian · debian_linux 2023-08-01 medium5.3 CVE-2023-4045 Offscreen Canvas did not properly track cross-origin tainting, which could have been used to access image data from another site in violation of same-origin po… mozilla · firefox, debian · debian_linux 2023-08-01 medium6.5 CVE-2023-37456 The session restore helper crashed whenever there was no parameter sent to the message handler. mozilla · firefox 2023-07-12 medium5.4 CVE-2023-37455 The permission request prompt from the site in the background tab was overlaid on top of the site in the foreground tab. mozilla · firefox 2023-07-12 medium6.5 CVE-2023-3482 When Firefox is configured to block storage of all cookies, it was still possible to store data in localstorage by using an iframe with a source of 'about:blan… mozilla · firefox 2023-07-05 medium6.5 CVE-2023-37210 A website could prevent a user from exiting full-screen mode via alert and prompt calls. mozilla · firefox 2023-07-05 medium6.5 CVE-2023-37206 Uploading files which contain symlinks may have allowed an attacker to trick a user into submitting sensitive data to a malicious website. mozilla · firefox 2023-07-05 medium6.5 CVE-2023-37205 The use of RTL Arabic characters in the address bar may have allowed for URL spoofing. mozilla · firefox 2023-07-05 medium6.5 CVE-2023-37204 A website could have obscured the fullscreen notification by using an option element by introducing lag via an expensive computational function. mozilla · firefox 2023-07-05 medium6.5 CVE-2023-37207 A website could have obscured the fullscreen notification by using a URL with a scheme handled by an external program, such as a mailto URL. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird +1 2023-07-05 medium6.1 CVE-2023-34415 When choosing a site-isolated process for a document loaded from a data: URL that was the result of a redirect, Firefox would load that document in the same pr… mozilla · firefox 2023-06-19 medium6.5 CVE-2023-29546 When recording the screen while in Private Browsing on Firefox for Android the address bar and keyboard were not hidden, potentially leaking sensitive informat… mozilla · firefox_focus, mozilla · firefox_mobile 2023-06-19 medium6.5 CVE-2023-29545 Similar to CVE-2023-28163, this time when choosing 'Save Link As', suggested filenames containing environment variable names would have resolved those in the c… mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2023-06-19 medium6.5 CVE-2023-32210 Documents were incorrectly assuming an ordering of principal objects when ensuring we were loading an appropriately privileged principal. mozilla · firefox 2023-06-19 medium5.3 CVE-2023-32208 Service workers could reveal script base URL due to dynamic `import()`. mozilla · firefox 2023-06-19 medium5.5 CVE-2023-29532 A local attacker can trick the Mozilla Maintenance Service into applying an unsigned update file by pointing the service at an update file on a malicious SMB s… mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2023-06-19 medium4.3 CVE-2023-32212 An attacker could have positioned a `datalist` element to obscure the address bar. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2023-06-02 medium6.5 CVE-2023-32211 A type checking bug would have led to invalid code being compiled. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2023-06-02 medium6.5 CVE-2023-32206 An out-of-bound read could have led to a crash in the RLBox Expat driver. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2023-06-02 medium4.3 CVE-2023-32205 In multiple cases browser prompts could have been obscured by popups controlled by content. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2023-06-02 medium6.5 CVE-2023-29549 Under certain circumstances, a call to the <code>bind</code> function may have resulted in the incorrect realm. mozilla · firefox, mozilla · firefox_mobile, mozilla · focus 2023-06-02 medium6.5 CVE-2023-29548 A wrong lowering instruction in the ARM64 Ion compiler resulted in a wrong optimization result. mozilla · firefox, mozilla · firefox_esr, mozilla · firefox_mobile +2 2023-06-02 medium6.5 CVE-2023-29547 When a secure cookie existed in the Firefox cookie jar an insecure cookie for the same domain could have been created, when it should have silently failed. mozilla · firefox, mozilla · firefox_esr, mozilla · focus 2023-06-02

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.