NetSight

Security Dashboard

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

Reset
108 matching advisories · page 4 of 4Index updated 7 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2023-35853 In Suricata before 6.0.13, an adversary who controls an external source of Lua rules may be able to execute Lua code. oisf · suricata 2023-06-19 high7.5 CVE-2023-35852 In Suricata before 6.0.13 (when there is an adversary who controls an external source of rules), a dataset filename, that comes from a rule, may trigger absolu… oisf · suricata 2023-06-19 high7.5 CVE-2020-19678 Directory Traversal vulnerability found in Pfsense v.2.1.3 and Pfsense Suricata v.1.4.6 pkg v.1.0.1 allows a remote attacker to obtain sensitive information vi… oisf · suricata, pfsense · pfsense, pfsense · suricata_package 2023-04-06 high7.5 CVE-2021-45098 An issue was discovered in Suricata before 6.0.4. oisf · suricata, debian · debian_linux 2021-12-16 critical9.8 CVE-2021-37592 Suricata before 5.0.8 and 6.x before 6.0.4 allows TCP evasion via a client with a crafted TCP/IP stack that can send a certain sequence of segments. oisf · suricata 2021-11-19 high7.5 CVE-2021-35063 Suricata before 5.0.7 and 6.x before 6.0.3 has a "critical evasion." oisf · suricata, debian · debian_linux, fedoraproject · fedora 2021-07-22 high7.5 CVE-2019-18625 An issue was discovered in Suricata 5.0.0. oisf · suricata, debian · debian_linux 2020-01-06 critical9.1 CVE-2019-18792 An issue was discovered in Suricata 5.0.0. oisf · suricata, debian · debian_linux 2020-01-06 medium5.3 CVE-2019-17420 In OISF LibHTP before 0.5.31, as used in Suricata 4.1.4 and other products, an HTTP protocol parsing error causes the http_header signature to not alert on a r… oisf · libhtp, suricata-ids · suricata 2019-10-10 high7.5 CVE-2019-1010279 Open Information Security Foundation Suricata prior to version 4.1.3 is affected by: Denial of Service - TCP/HTTP detection bypass. oisf · suricata 2019-07-18 high7.5 CVE-2019-1010251 Open Information Security Foundation Suricata prior to version 4.1.2 is affected by: Denial of Service - DNS detection bypass. oisf · suricata 2019-07-18 high7.5 CVE-2019-10050 A buffer over-read issue was discovered in Suricata 4.1.x before 4.1.4. oisf · suricata 2019-05-13 critical9.8 CVE-2018-10244 Suricata version 4.0.4 incorrectly handles the parsing of an EtherNet/IP PDU. oisf · suricata 2019-04-04 critical9.8 CVE-2018-10243 htp_parse_authorization_digest in htp_parsers.c in LibHTP 0.5.26 allows remote attackers to cause a heap-based buffer over-read via an authorization digest hea… oisf · libhtp 2019-04-04 high7.5 CVE-2018-10242 Suricata version 4.0.4 incorrectly handles the parsing of the SSH banner. oisf · suricata, debian · debian_linux 2019-04-04 high7.8 CVE-2018-1000167 OISF suricata-update unsafely deserializes YAML data pip · suricata-update 2018-04-18 high7.5 CVE-2015-0928 libhtp 0.5.15 allows remote attackers to cause a denial of service (NULL pointer dereference). oisf · libhtp 2017-08-28 medium5.0 CVE-2013-5919 Suricata before 1.4.6 allows remote attackers to cause a denial of service (crash) via a malformed SSL record. oisf · suricata, openinfosecfoundation · suricata 2014-05-30

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.