NetSight

Security Dashboard

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

Reset
56 matching advisories · page 2 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2024-54151 Directus allows unauthenticated access to WebSocket events and operations npm · directus, npm · @directus/api 2024-12-09 medium5.7 CVE-2024-54128 Directus has an HTML Injection in Comment npm · @directus/app, npm · directus 2024-12-05 medium4.2 CVE-2024-47822 Directus inserts access token from query string into logs npm · @directus/api 2024-10-08 medium5.0 CVE-2024-46990 Directus vulnerable to SSRF Loopback IP filter bypass npm · directus, npm · @directus/api 2024-09-18 high7.4 CVE-2024-45596 Session is cached for OpenID and OAuth2 if `redirect` is not used npm · directus, npm · @directus/api 2024-09-10 medium4.1 CVE-2024-6534 Directus has an insecure object reference via PATH presets npm · directus 2024-08-15 medium5.4 CVE-2024-6533 Directus has a DOM-Based cross-site scripting (XSS) via layout_options npm · directus 2024-08-15 high7.5 CVE-2024-39896 Directus Allows Single Sign-On User Enumeration npm · directus 2024-07-08 high6.5 CVE-2024-39895 Directus GraphQL Field Duplication Denial of Service (DoS) npm · @directus/env 2024-07-08 high6.3 CVE-2024-39701 Directus incorrectly handles `_in` filter npm · directus 2024-07-08 medium5.0 CVE-2024-39699 Directus Blind SSRF On File Import npm · @directus/api 2024-07-08 high7.5 CVE-2024-36128 Directus is soft-locked by providing a string value to random string util npm · directus 2024-06-03 medium5.4 CVE-2024-34709 Directus Lacks Session Tokens Invalidation npm · directus 2024-05-13 medium4.9 CVE-2024-34708 Directus allows redacted data extraction on the API through "alias" npm · directus 2024-05-13 medium5.4 CVE-2024-28239 URL Redirection to Untrusted Site in OAuth2/OpenID in directus npm · directus 2024-03-12 low2.3 CVE-2024-28238 Session Token in URL in directus npm · directus 2024-03-12 medium5.3 CVE-2024-27296 Directus version number disclosure npm · directus 2024-03-01 high8.2 CVE-2024-27295 Directus has MySQL accent insensitive email matching npm · directus 2024-03-01 high7.5 CVE-2023-45820 Directus crashes on invalid WebSocket message npm · directus 2023-10-19 medium5.7 CVE-2023-38503 Incorrect Permission Checking for GraphQL Subscriptions npm · directus 2023-07-25 medium6.5 CVE-2020-19850 Directus API vulnerable to denial of service npm · directus 2023-04-04 medium4.2 CVE-2023-28443 directus vulnerable to Insertion of Sensitive Information into Log File npm · directus 2023-03-23 medium6.5 CVE-2023-27481 Directus vulnerable to extraction of password hashes through export querying npm · directus 2023-03-07 medium5.0 CVE-2023-26492 Directus vulnerable to Server-Side Request Forgery On File Import npm · directus 2023-03-03 medium6.5 CVE-2022-36031 Directus vulnerable to unhandled exception on illegal filename_disk value npm · directus 2022-08-19 critical9.8 CVE-2022-26969 Insecure default value for CORS configuration npm · directus 2022-04-05

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.