NetSight

Security Dashboard

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

Reset
453 matching advisories · page 14 of 16Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2018-0732 During key agreement in a TLS handshake using a DH(E) based ciphersuite a malicious server can send a very large prime value to the client. openssl · openssl, canonical · ubuntu_linux, debian · debian_linux +1 2018-06-12 medium6.5 CVE-2017-16024 Tmp files readable by other users in sync-exec npm · sync-exec 2018-06-04 high8.1 CVE-2016-10626 mystem3 is a NodeJS wrapper for the Yandex MyStem 3. npm · mystem3 2018-06-01 high8.1 CVE-2016-10622 nodeschnaps is a NodeJS compatibility layer for Java (Rhino). npm · nodeschnaps 2018-06-01 high8.1 CVE-2016-10618 node-browser is a wrapper webdriver by nodejs. npm · node-browser 2018-06-01 high8.1 CVE-2016-10593 ibapi is an Interactive Brokers API addon for NodeJS. npm · ibapi 2018-05-29 high8.1 CVE-2016-10578 unicode loads unicode data downloaded from unicode.org into nodejs. npm · unicode 2018-05-29 high8.8 CVE-2018-7160 Withdrawn Advisory: Node.js Inspector RCE via DNS Rebinding npm · node-inspector 2018-05-17 medium5.3 CVE-2018-7159 The HTTP parser in all current versions of Node.js ignores spaces in the `Content-Length` header, allowing input such as `Content-Length: 1 2` to be interprete… nodejs · node.js 2018-05-17 high7.5 CVE-2018-7158 The `'path'` module in the Node.js 4.x release line contains a potential regular expression denial of service (ReDoS) vector. nodejs · node.js 2018-05-17 high7.5 CVE-2018-1000168 nghttp2 version >= 1.10.0 and nghttp2 <= v1.31.0 contains an Improper Input Validation CWE-20 vulnerability in ALTSVC frame handling that can result in segment… nghttp2 · nghttp2, nodejs · node.js, debian · debian_linux 2018-05-08 low3.1 CVE-2017-15897 Node.js had a bug in versions 8.X and 9.X which caused buffers to not be initialized when the encoding for the fill value did not match the encoding specified. nodejs · node.js 2017-12-11 critical9.1 CVE-2017-15896 Node.js was affected by OpenSSL vulnerability CVE-2017-3737 in regards to the use of SSL_read() due to TLS handshake failure. nodejs · node.js 2017-12-11 medium5.9 CVE-2017-3738 There is an overflow bug in the AVX2 Montgomery multiplication procedure used in exponentiation with 1024-bit moduli. openssl · openssl, debian · debian_linux, nodejs · node.js 2017-12-07 critical9.8 CVE-2017-1000228 nodejs ejs versions older than 2.5.3 is vulnerable to remote code execution due to weak input validation in ejs.renderFile() function npm · ejs 2017-11-17 high7.5 CVE-2017-1000189 nodejs ejs version older than 2.5.5 is vulnerable to a denial-of-service due to weak input validation in the ejs.renderFile() npm · ejs 2017-11-17 medium6.1 CVE-2017-1000188 nodejs ejs version older than 2.5.5 is vulnerable to a Cross-site-scripting in the ejs.renderFile() resulting in code injection npm · ejs 2017-11-17 high7.5 CVE-2017-14919 Node.js before 4.8.5, 6.x before 6.11.5, and 8.x before 8.8.0 allows remote attackers to cause a denial of service (uncaught exception and crash) by leveraging… nodejs · node.js 2017-10-30 high7.5 CVE-2014-3744 Directory Traversal in st npm · st 2017-10-23 high7.5 CVE-2015-7384 Node.js 4.0.0, 4.1.0, and 4.1.1 allows remote attackers to cause a denial of service. nodejs · node.js 2017-10-10 high7.5 CVE-2017-14849 Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was incompatible with the pathname validation … nodejs · node.js 2017-09-28 medium6.5 CVE-2015-2927 node 0.3.2 and URONode before 1.0.5r3 allows remote attackers to cause a denial of service (bandwidth consumption). nodejs · node.js, uronode · uro_node, debian · debian_linux 2017-09-20 high7.5 CVE-2017-11499 Node.js v4.0 through v4.8.3, all versions of v5.x, v6.0 through v6.11.0, v7.0 through v7.10.0, and v8.0 through v8.1.3 was susceptible to hash flooding remote … nodejs · node.js 2017-07-25 high7.5 CVE-2017-1000381 The c-ares function `ares_parse_naptr_reply()`, which is used for parsing NAPTR responses, could be triggered to read memory outside of the given input buffer … c-ares · c-ares, c-ares_project · c-ares, nodejs · node.js 2017-07-07 critical9.8 CVE-2017-7474 keycloak-connect and keycloak-js improperly handle invalid tokens npm · keycloak-connect, npm · keycloak-js 2017-05-12 medium5.9 CVE-2016-7055 There is a carry propagating bug in the Broadwell-specific Montgomery multiplication procedure in OpenSSL 1.0.2 and 1.1.0 before 1.1.0c that handles input leng… openssl · openssl, nodejs · node.js 2017-05-04 medium5.9 CVE-2017-3732 There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL 1.0.2 before 1.0.2k and 1.1.0 before 1.1.0d. openssl · openssl, nodejs · node.js 2017-05-04 high7.5 CVE-2017-3731 If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to per… openssl · openssl, nodejs · node.js 2017-05-04 high7.5 CVE-2015-8860 Symlink Arbitrary File Overwrite in tar npm · tar 2017-01-23 high7.5 CVE-2015-8855 Regular Expression Denial of Service in semver npm · semver 2017-01-23

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.