NetSight

Security Dashboard

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

Reset
169 matching advisories · page 6 of 6Index updated 7 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-mxfv-rxxq-6757 Malware in grenache-nodejs-utpMalware npm · grenache-nodejs-utp 2022-06-20 critical GHSA-4wrw-q88x-9656 Malware in remote-pay-cloud-nodejs-exampleMalware npm · remote-pay-cloud-nodejs-example 2022-06-20 critical GHSA-c662-grhj-245p Malware in courier-plugin-sdk-nodejsMalware npm · courier-plugin-sdk-nodejs 2022-06-20 critical GHSA-3854-g6w5-3wf9 Malware in nodejs-gcloud-pubsub-moduleMalware npm · nodejs-gcloud-pubsub-module 2022-06-20 critical GHSA-p37x-p4j4-4rm3 Malware in slint-config-nodejsMalware npm · slint-config-nodejs 2022-06-20 critical GHSA-8362-7fhw-3cpm Malware in metadata-api-nodejsMalware npm · metadata-api-nodejs 2022-06-20 critical GHSA-h6m6-3p6p-7cmq Malware in nodejs-driverMalware npm · nodejs-driver 2022-06-20 critical9.8 CVE-2021-22930 Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory corruption, to chang… nodejs · node.js, netapp · nextgen_api, siemens · sinec_infrastructure_network_services +1 2021-10-07 critical10.0 CVE-2021-39199 remark-html is an open source nodejs library which compiles Markdown to HTML. npm · remark-html 2021-09-07 critical9.8 CVE-2021-22931 Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to Remote Code Execution, XSS, Application crashes due to missing input validation of host names retu… nodejs · node.js, netapp · active_iq_unified_manager, netapp · nextgen_api +7 2021-08-16 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 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 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 critical9.8 CVE-2017-7474 keycloak-connect and keycloak-js improperly handle invalid tokens npm · keycloak-connect, npm · keycloak-js 2017-05-12 critical9.8 CVE-2016-5180 Heap-based buffer overflow in the ares_create_query function in c-ares 1.x before 1.12.0 allows remote attackers to cause a denial of service (out-of-bounds wr… c-ares · c-ares, c-ares_project · c-ares, debian · debian_linux +2 2016-10-03 critical9.8 CVE-2016-6303 Integer overflow in the MDC2_Update function in crypto/mdc2/mdc2dgst.c in OpenSSL before 1.1.0 allows remote attackers to cause a denial of service (out-of-bou… nodejs · node.js, openssl · openssl 2016-09-16 critical9.8 CVE-2015-6764 The BasicJsonStringifier::SerializeJSArray function in json-stringifier.h in the JSON stringifier in Google V8, as used in Google Chrome before 47.0.2526.73, i… google · chrome, nodejs · node.js, debian · debian_linux 2015-12-06 critical10.0 CVE-2015-0278 libuv before 0.10.34 does not properly drop group privileges, which allows context-dependent attackers to gain privileges via unspecified vectors. fedoraproject · fedora, libuv_project · libuv, nodejs · node.js 2015-05-18

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.