NetSight

Security Dashboard

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

Reset
167 matching advisories · page 6 of 6Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2019-17640 Path Traversal in Eclipse Vert maven · io.vertx:vertx-web 2020-10-15 critical9.4 CVE-2019-17638 Operation on a Resource after Expiration or Release in Jetty Server maven · org.eclipse.jetty:jetty-server 2020-07-09 critical9.8 CVE-2020-12821 Gossipsub 1.0 does not properly resist invalid message spam, such as an eclipse attack or a sybil attack. protocol · gossipsub 2020-07-07 critical9.8 CVE-2014-9390 JGit Improper Input Validation vulnerability maven · org.eclipse.jgit:org.eclipse.jgit, pip · mercurial 2020-02-12 critical9.0 CVE-2019-17634 Eclipse Memory Analyzer version 1.9.1 and earlier is subject to a cross site scripting (XSS) vulnerability when generating an HTML report from a malicious heap… eclipse · memory_analyzer 2020-01-17 critical9.1 CVE-2019-17631 From Eclipse OpenJ9 0.15 to 0.16, access to diagnostic operations such as causing a GC or creating a diagnostic file are permitted without any privilege checks. eclipse · openj9, redhat · satellite, redhat · enterprise_linux +4 2019-10-17 critical9.8 CVE-2019-11772 In Eclipse OpenJ9 prior to 0.15, the String.getBytes(int, int, byte[], int) method does not verify that the provided byte array is non-null nor that the provid… eclipse · openj9 2019-07-17 critical9.8 CVE-2018-12549 In Eclipse OpenJ9 version 0.11.0, the OpenJ9 JIT compiler may incorrectly omit a null check on the receiver object of an Unsafe call when accelerating it. eclipse · openj9, redhat · satellite, redhat · enterprise_linux_desktop +2 2019-02-11 critical9.8 CVE-2018-12547 In Eclipse OpenJ9, prior to the 0.12.0 release, the jio_snprintf() and jio_vsnprintf() native methods ignored the length parameter. eclipse · openj9, redhat · satellite, redhat · enterprise_linux_desktop +2 2019-02-11 critical9.8 CVE-2018-12548 In OpenJDK + Eclipse OpenJ9 version 0.11.0 builds, the public jdk.crypto.jniprovider.NativeCrypto class contains public static natives which accept pointer val… eclipse · openj9 2019-01-31 critical9.8 CVE-2018-12544 Moderate severity vulnerability that affects io.vertx:vertx-core maven · io.vertx:vertx-core 2018-10-10 critical9.8 CVE-2018-12542 Eclipse Vert.x does not properly neutralize '' (forward slashes) sequences that can resolve to an external location maven · io.vertx:vertx-web 2018-10-10 critical10.0 CVE-2018-1000644 Eclipse RDF4j vulnerable to XML External Entity maven · org.eclipse.rdf4j:rdf4j-runtime 2018-08-20 critical9.8 CVE-2017-7658 Jetty vulnerable to authorization bypass due to inconsistent HTTP request handling (HTTP Request Smuggling) maven · org.eclipse.jetty:jetty-server 2018-06-26 critical9.8 CVE-2017-7657 Critical severity vulnerability that affects org.eclipse.jetty:jetty-server maven · org.eclipse.jetty:jetty-server 2018-06-26 critical9.8 CVE-2017-7649 The network enabled distribution of Kura before 2.1.0 takes control over the device's firewall setup but does not allow IPv6 firewall rules to be configured. eclipse · kura 2017-09-11 critical9.8 CVE-2016-4800 Jetty contains an alias issue that could allow unauthenticated remote code execution due to specially crafted request maven · org.eclipse.jetty:jetty-server 2017-04-13

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.