NetSight

Security Dashboard

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

Reset
1,300 matching advisories · page 19 of 44Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2023-37212 Memory safety bugs present in Firefox 114. mozilla · firefox 2023-07-05 high8.8 CVE-2023-37211 Memory safety bugs present in Firefox 114, Firefox ESR 102.12, and Thunderbird 102.12. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird +1 2023-07-05 high8.8 CVE-2023-37209 A use-after-free condition existed in `NotifyOnHistoryReload` where a `LoadingSessionHistoryEntry` object was freed and a reference to that object remained. mozilla · firefox 2023-07-05 high7.8 CVE-2023-37203 Insufficient validation in the Drag and Drop API in conjunction with social engineering, may have allowed an attacker to trick end-users into creating a shortc… mozilla · firefox 2023-07-05 high7.8 CVE-2023-37208 When opening Diagcab files, Firefox did not warn the user that these files may contain malicious code. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird +1 2023-07-05 high8.8 CVE-2023-37202 Cross-compartment wrappers wrapping a scripted proxy could have caused objects from other compartments to be stored in the main compartment resulting in a use-… mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird +1 2023-07-05 high8.8 CVE-2023-37201 An attacker could have triggered a use-after-free condition when creating a WebRTC connection over HTTPS. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird +1 2023-07-05 high7.5 CVE-2023-25747 A potential use-after-free in libaudio was fixed by disabling the AAudio backend when running on Android API below version 30. mozilla · firefox_mobile 2023-06-19 high7.5 CVE-2023-25733 The return value from `gfx::SourceSurfaceSkia::Map()` wasn't being verified which could have potentially lead to a null pointer dereference. mozilla · firefox 2023-06-19 high7.5 CVE-2023-32214 Protocol handlers `ms-cxh` and `ms-cxh-full` could have been leveraged to trigger a denial of service. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2023-06-19 high7.5 CVE-2023-32209 A maliciously crafted favicon could have led to an out of memory crash. mozilla · firefox 2023-06-19 high8.8 CVE-2023-32215 Mozilla developers and community members Gabriele Svelto, Andrew Osmond, Emily McDonough, Sebastian Hengst, Andrew McCreight and the Mozilla Fuzzing Team repor… mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2023-06-02 high8.8 CVE-2023-32213 When reading a file, an uninitialized value could have been used as read limit. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2023-06-02 high8.8 CVE-2023-32207 A missing delay in popup notifications could have made it possible for an attacker to trick a user into granting permissions. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2023-06-02 high8.8 CVE-2023-29551 Memory safety bugs present in Firefox 111. mozilla · firefox, mozilla · firefox_mobile, mozilla · focus 2023-06-02 high8.8 CVE-2023-29550 Memory safety bugs present in Firefox 111 and Firefox ESR 102.9. mozilla · firefox, mozilla · firefox_esr, mozilla · firefox_mobile +2 2023-06-02 high8.8 CVE-2023-29543 An attacker could have caused memory corruption and a potentially exploitable use-after-free of a pointer in a global object's debugger vector. mozilla · firefox, mozilla · firefox_mobile, mozilla · focus 2023-06-02 high8.8 CVE-2023-29541 Firefox did not properly handle downloads of files ending in <code>.desktop</code>, which can be interpreted to run attacker-controlled commands. mozilla · firefox, mozilla · firefox_esr, mozilla · firefox_mobile +2 2023-06-02 high8.8 CVE-2023-29539 When handling the filename directive in the Content-Disposition header, the filename would be truncated if the filename contained a NULL character. mozilla · firefox, mozilla · firefox_esr, mozilla · firefox_mobile +2 2023-06-02 high7.5 CVE-2023-29537 Multiple race conditions in the font initialization could have led to memory corruption and execution of attacker-controlled code. mozilla · firefox, mozilla · firefox_mobile, mozilla · focus 2023-06-02 high8.8 CVE-2023-29536 An attacker could cause the memory manager to incorrectly free a pointer that addresses attacker-controlled memory, resulting in an assertion, memory corruptio… mozilla · firefox, mozilla · firefox_esr, mozilla · firefox_mobile +2 2023-06-02 high8.8 CVE-2023-28177 Memory safety bugs present in Firefox 110. mozilla · firefox 2023-06-02 high8.8 CVE-2023-28176 Memory safety bugs present in Firefox 110 and Firefox ESR 102.8. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2023-06-02 high8.8 CVE-2023-28162 While implementing AudioWorklets, some code may have casted one type to another, invalid, dynamic type. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird 2023-06-02 high8.8 CVE-2023-28161 If temporary "one-time" permissions, such as the ability to use the Camera, were granted to a document loaded using a file: URL, that permission persisted in t… mozilla · firefox 2023-06-02 high8.8 CVE-2023-25746 Memory safety bugs present in Firefox ESR 102.7. mozilla · firefox_esr, mozilla · thunderbird 2023-06-02 high8.8 CVE-2023-25745 Memory safety bugs present in Firefox 109. mozilla · firefox 2023-06-02 high8.8 CVE-2023-25744 Mmemory safety bugs present in Firefox 109 and Firefox ESR 102.7. mozilla · firefox, mozilla · firefox_esr 2023-06-02 high7.5 CVE-2023-25743 A lack of in app notification for entering fullscreen mode could have lead to a malicious website spoofing browser chrome.<br>*This bug only affects Firefox Fo… mozilla · firefox_focus 2023-06-02 high8.8 CVE-2023-25740 After downloading a Windows <code>.scf</code> script from the local filesystem, an attacker could supply a remote path that would lead to unexpected network re… mozilla · firefox 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.