NetSight

Security Dashboard

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

Reset
453 matching advisories · page 13 of 16Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.1 CVE-2020-8174 napi_get_value_string_*() allows various kinds of memory corruption in node < 10.21.0, 12.18.0, and < 14.4.0. nodejs · node.js, oracle · banking_extensibility_workbench, oracle · blockchain_platform +6 2020-07-24 high7.4 CVE-2020-8172 TLS session reuse can lead to host certificate verification bypass in node version < 12.18.0 and < 14.4.0. nodejs · node.js, oracle · banking_extensibility_workbench, oracle · blockchain_platform +2 2020-06-08 low3.7 CVE-2020-11080 In nghttp2 before version 1.41.0, the overly large HTTP/2 SETTINGS frame payload causes denial of service. nghttp2 · nghttp2, debian · debian_linux, opensuse · leap +7 2020-06-03 high7.8 CVE-2019-4001 Improper input validation in Druva inSync Client 6.5.0 allows a local, authenticated attacker to execute arbitrary NodeJS code. druva · insync 2020-03-24 high8.8 CVE-2020-10531 An issue was discovered in International Components for Unicode (ICU) for C/C++ through 66.1. icu-project · international_components_for_unicode, redhat · enterprise_linux_desktop, redhat · enterprise_linux_server +8 2020-03-12 high8.1 CVE-2014-9748 The uv_rwlock_t fallback implementation for Windows XP and Server 2003 in libuv before 1.7.4 does not properly prevent threads from releasing the locks of othe… libuv · libuv, nodejs · node.js 2020-02-11 critical9.8 CVE-2019-15606 Including trailing white space in HTTP header values in Nodejs 10, 12, and 13 causes bypass of authorization based on header value comparisons nodejs · node.js, oracle · communications_cloud_native_core_network_function_cloud_native_environment, oracle · graalvm +4 2020-02-07 critical9.8 CVE-2019-15605 HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed nodejs · node.js, debian · debian_linux, fedoraproject · fedora +9 2020-02-07 high7.5 CVE-2019-15604 Improper Certificate Validation in Node.js 10, 12, and 13 causes the process to abort when sending a crafted X.509 certificate nodejs · node.js, debian · debian_linux, opensuse · leap +7 2020-02-07 high8.8 CVE-2020-7596 Improper Neutralization of Special Elements in Output Used by a Downstream Component in Codecov npm · codecov 2020-01-25 high7.5 CVE-2019-9512 golang.org/x/net/http vulnerable to ping floods go · golang.org/x/net 2019-08-13 medium6.5 CVE-2018-21270 Out-of-bounds Read in stringstream npm · stringstream 2019-06-20 medium6.1 CVE-2019-12047 Gridea v0.8.0 has an XSS vulnerability through which the Nodejs module can be called to achieve arbitrary code execution, as demonstrated by child_process.exec… gridea · gridea 2019-05-13 high7.5 CVE-2019-5739 Keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 minutes in Node.js 6.16.0 and earlier. nodejs · node.js, opensuse · leap 2019-03-28 high7.5 CVE-2019-5737 In Node.js including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1, an attacker can cause a Denial of Service (DoS) by est… nodejs · node.js, opensuse · leap 2019-03-28 medium4.3 CVE-2018-12123 Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Hostname spoofing in URL parser for javascript protocol: If a Node.js application is… nodejs · node.js 2018-11-28 high7.5 CVE-2018-12122 Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Slowloris HTTP Denial of Service: An attacker can cause a Denial of Service (DoS) by… nodejs · node.js, suse · suse_enterprise_storage, suse · suse_linux_enterprise_server +1 2018-11-28 high7.5 CVE-2018-12121 Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Denial of Service with large HTTP headers: By using a combination of many requests w… nodejs · node.js, redhat · enterprise_linux, redhat · enterprise_linux_desktop +5 2018-11-28 high8.1 CVE-2018-12120 Node.js: All versions prior to Node.js 6.15.0: Debugger port 5858 listens on any interface by default: When the debugger is enabled with `node --debug` or `nod… nodejs · node.js 2018-11-28 high7.5 CVE-2018-12116 Node.js: All versions prior to Node.js 6.15.0 and 8.14.0: HTTP request splitting: If Node.js can be convinced to use unsanitized user-provided Unicode data for… nodejs · node.js, suse · suse_enterprise_storage, suse · suse_linux_enterprise_server +1 2018-11-28 medium4.7 CVE-2018-5407 Simultaneous Multi-threading (SMT) in processors can enable local users to exploit software vulnerable to timing attacks via a side-channel timing attack on 'p… canonical · ubuntu_linux, debian · debian_linux, nodejs · node.js +9 2018-11-15 medium5.9 CVE-2018-0734 The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. openssl · openssl, canonical · ubuntu_linux, debian · debian_linux +9 2018-10-30 medium5.9 CVE-2018-0735 The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a timing side channel attack. openssl · openssl, canonical · ubuntu_linux, debian · debian_linux +9 2018-10-29 medium5.3 CVE-2016-1000232 NodeJS Tough-Cookie version 2.2.2 contains a Regular Expression Parsing vulnerability in HTTP request Cookie Header parsing that can result in Denial of Servic… npm · tough-cookie 2018-09-05 high7.5 CVE-2018-7166 In all versions of Node.js 10 prior to 10.9.0, an argument processing flaw can cause `Buffer.alloc()` to return uninitialized memory. nodejs · node.js 2018-08-21 high7.5 CVE-2018-12115 In all versions of Node.js prior to 6.14.4, 8.11.4 and 10.9.0 when used with UCS-2 encoding (recognized by Node.js under the names `'ucs2'`, `'ucs-2'`, `'utf16… nodejs · node.js, redhat · openshift_container_platform 2018-08-21 high7.5 CVE-2018-7167 Calling Buffer.fill() or Buffer.alloc() with some parameters can lead to a hang which could result in a Denial of Service. nodejs · node.js 2018-06-13 high7.5 CVE-2018-7164 Node.js versions 9.7.0 and later and 10.x are vulnerable and the severity is MEDIUM. nodejs · node.js 2018-06-13 high7.5 CVE-2018-7162 All versions of Node.js 9.x and 10.x are vulnerable and the severity is HIGH. nodejs · node.js 2018-06-13 high7.5 CVE-2018-7161 All versions of Node.js 8.x, 9.x, and 10.x are vulnerable and the severity is HIGH. nodejs · node.js 2018-06-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.