NetSight

Security Dashboard

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

Reset
169 matching advisories · page 5 of 6Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2023-32002 The use of `Module._load()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. nodejs · node.js 2023-08-21 critical GHSA-8w2x-5hm2-2ww6 Malware in wasabi-nodejsMalware npm · wasabi-nodejs 2023-08-09 critical9.8 CVE-2023-26563 The Syncfusion EJ2 Node File Provider 0102271 is vulnerable to filesystem-server.js directory traversal. syncfusion · nodejs_file_system_provider 2023-07-12 critical GHSA-w855-7wcv-fv7v Malware in nodejs-encrypt-agentMalware npm · nodejs-encrypt-agent 2023-04-26 critical GHSA-4f44-57v5-8mch Malware in nodejs-cookie-proxy-agentMalware npm · nodejs-cookie-proxy-agent 2023-04-26 critical GHSA-gjjj-m5j2-h9fv Malware in ynodejs_mod_logMalware npm · ynodejs_mod_log 2023-04-12 critical9.1 CVE-2022-35255 A weak randomness in WebCrypto keygen vulnerability exists in Node.js 18 due to a change with EntropySource() in SecretKeyGenTraits::DoKeyGen() in src/crypto/c… nodejs · node.js, siemens · sinec_ins, debian · debian_linux 2022-12-05 critical9.8 CVE-2022-3602 A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. rust · openssl-src 2022-11-01 critical9.6 CVE-2022-39266 isolated-vm is a library for nodejs which gives the user access to v8's Isolate interface. npm · isolated-vm 2022-09-29 critical GHSA-m29v-hh6p-5v86 Malware in google-auth-library-nodejsMalware npm · google-auth-library-nodejs 2022-09-07 critical GHSA-7mcr-wpf2-4qgr Malware in nodejs-colorMalware npm · nodejs-color 2022-08-16 critical GHSA-6j6f-3637-w8q9 Malware in quest-bee-nodejsMalware npm · quest-bee-nodejs 2022-08-10 critical GHSA-6j3w-rrjf-rxc6 Malware in nodejs-emailMalware npm · nodejs-email 2022-07-21 critical9.1 CVE-2022-32214 llhttp allows HTTP Request Smuggling via Improper Delimiting of Header Fields npm · llhttp 2022-07-14 critical9.1 CVE-2022-32213 llhttp allows HTTP Request Smuggling via Flawed Parsing of Transfer-Encoding npm · llhttp 2022-07-14 critical GHSA-frf6-jvh9-qmq4 Malware in nodejs-docs-samples-iot-mqtt-exampleMalware npm · nodejs-docs-samples-iot-mqtt-example 2022-06-20 critical GHSA-6cp8-mvhq-853q Malware in finastra-nodejs-libsMalware npm · finastra-nodejs-libs 2022-06-20 critical GHSA-vx89-6qgf-whfx Malware in facebook-nodejs-business-sdk-testsMalware npm · facebook-nodejs-business-sdk-tests 2022-06-20 critical GHSA-46pr-2chf-cc7g Malware in paytm-mini-programs-nodejs-sdkMalware npm · paytm-mini-programs-nodejs-sdk 2022-06-20 critical GHSA-r2rj-p4c3-jj9w Malware in output-scrubber-nodejsMalware npm · output-scrubber-nodejs 2022-06-20 critical GHSA-mxvg-62j8-6hwq Malware in wallet-nodejs-bindingMalware npm · wallet-nodejs-binding 2022-06-20 critical GHSA-4hg9-qmcg-3x8h Malware in nodejs_net_serverMalware npm · nodejs_net_server 2022-06-20 critical GHSA-36hj-gchg-gr26 Malware in redox-sample-nodejsMalware npm · redox-sample-nodejs 2022-06-20 critical GHSA-2mpg-vvhj-xc8c Malware in capacitybot-cf-nodejs-fctMalware npm · capacitybot-cf-nodejs-fct 2022-06-20 critical GHSA-722h-q8x2-r666 Malware in myjohndeereapi-oauth2-nodejs-exampleMalware npm · myjohndeereapi-oauth2-nodejs-example 2022-06-20 critical GHSA-52pc-jpq8-hrpj Malware in invision-nodejs-test-utilsMalware npm · invision-nodejs-test-utils 2022-06-20 critical GHSA-cwmw-286w-3whf Malware in grenache-nodejs-example-fib-clientMalware npm · grenache-nodejs-example-fib-client 2022-06-20 critical GHSA-2cpr-2w4c-9rjq Malware in grenache-nodejs-example-fib-serverMalware npm · grenache-nodejs-example-fib-server 2022-06-20 critical GHSA-gx3j-j24p-ggp9 Malware in grenache-nodejs-fib-serverMalware npm · grenache-nodejs-fib-server 2022-06-20 critical GHSA-j2rc-8j33-jf2c Malware in grenache-nodejs-fib-clientMalware npm · grenache-nodejs-fib-client 2022-06-20

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.