NetSight

Security Dashboard

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

Reset
96 matching advisories · page 3 of 4Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.0 CVE-2022-27820 Improper Certificate Validation in OWASP ZAP maven · org.zaproxy:zap 2022-03-24 high7.5 CVE-2021-42717 ModSecurity 3.x through 3.0.5 mishandles excessively nested JSON objects. owasp · modsecurity, trustwave · modsecurity, f5 · nginx_modsecurity_waf +3 2021-12-07 high7.1 CVE-2021-43577 XXE vulnerability in Jenkins OWASP Dependency-Check Plugin maven · org.jenkins-ci.plugins:dependency-check-jenkins-plugin 2021-11-12 critical9.8 CVE-2021-35368 OWASP ModSecurity Core Rule Set 3.1.x before 3.1.2, 3.2.x before 3.2.1, and 3.3.x before 3.3.2 is affected by a Request Body Bypass via a trailing pathname. owasp · owasp_modsecurity_core_rule_set, fedoraproject · fedora, debian · debian_linux 2021-11-05 critical9.8 CVE-2021-42575 Policies not properly enforced in OWASP Java HTML Sanitizer maven · com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer 2021-10-18 high8.8 CVE-2021-28490 Cross-Site Request Forgery in OWASP CSRFGuard maven · org.owasp:csrfguard 2021-08-19 medium6.1 CVE-2021-35043 Cross-site Scripting in OWASP AntiSamy maven · org.owasp.antisamy:antisamy 2021-07-19 medium5.9 CVE-2010-3300 Padding oracle attacks maven · org.owasp.esapi:esapi 2021-06-22 medium5.3 CVE-2019-25043 ModSecurity 3.x before 3.0.4 mishandles key-value pair parsing, as demonstrated by a "string index out of range" error and worker-process crash for a "Cookie: … owasp · modsecurity 2021-05-06 high8.8 CVE-2021-21633 CSRF vulnerability and in Jenkins OWASP Dependency-Track Plugin allow capturing credentials maven · org.jenkins-ci.plugins:dependency-track 2021-03-30 medium6.5 CVE-2021-21632 Missing permission checks in Jenkins OWASP Dependency-Track Plugin allow capturing credentials maven · org.jenkins-ci.plugins:dependency-track 2021-03-30 high7.5 CVE-2021-23900 Uncaught Exception leading to Denial of Service in json-sanitizer maven · com.mikesamuel:json-sanitizer 2021-01-13 critical9.8 CVE-2021-23899 Arbitrary code injection in json-sanitizer maven · com.mikesamuel:json-sanitizer 2021-01-13 high7.5 CVE-2020-15598 Trustwave ModSecurity 3.x through 3.0.4 allows denial of service via a special request. owasp · modsecurity, debian · debian_linux 2020-10-06 medium6.1 CVE-2020-13973 Cross-site scripting in json-sanitizer maven · com.mikesamuel:json-sanitizer 2020-06-09 high7.5 CVE-2019-19886 Trustwave ModSecurity 3.0.0 through 3.0.3 allows an attacker to send crafted requests that may, when sent quickly in large volumes, lead to the server becoming… owasp · modsecurity, fedoraproject · fedora 2020-01-21 medium5.4 CVE-2019-1020007 Dependency-Track before 3.5.1 allows XSS. owasp · dependency-track 2019-07-29 high7.5 CVE-2019-13464 An issue was discovered in OWASP ModSecurity Core Rule Set (CRS) 3.0.2. modsecurity · owasp_modsecurity_core_rule_set 2019-07-09 medium5.3 CVE-2019-11391 An issue was discovered in OWASP ModSecurity Core Rule Set (CRS) through 3.1.0. modsecurity · owasp_modsecurity_core_rule_set 2019-04-21 medium5.3 CVE-2019-11390 An issue was discovered in OWASP ModSecurity Core Rule Set (CRS) through 3.1.0. modsecurity · owasp_modsecurity_core_rule_set 2019-04-21 medium5.3 CVE-2019-11389 An issue was discovered in OWASP ModSecurity Core Rule Set (CRS) through 3.1.0. modsecurity · owasp_modsecurity_core_rule_set 2019-04-21 medium5.3 CVE-2019-11388 An issue was discovered in OWASP ModSecurity Core Rule Set (CRS) through 3.1.0. modsecurity · owasp_modsecurity_core_rule_set 2019-04-21 medium5.3 CVE-2019-11387 An issue was discovered in OWASP ModSecurity Core Rule Set (CRS) through 3.1.0. modsecurity · owasp_modsecurity_core_rule_set 2019-04-21 high8.8 CVE-2019-1003060 Jenkins Official OWASP ZAP Plugin stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with … maven · org.jenkins-ci.plugins:zap 2019-04-04 high7.5 CVE-2018-16384 A SQL injection bypass (aka PL1 bypass) exists in OWASP ModSecurity Core Rule Set (owasp-modsecurity-crs) through v3.1.0-rc3 via {`a`b} where a is a special fu… owasp · owasp_modsecurity_core_rule_set 2018-09-03 medium CVE-2018-1000643 Moderate severity vulnerability that affects org.owasp.antisamy:antisamy maven · org.owasp.antisamy:antisamy 2018-08-20 medium6.1 CVE-2018-13065 ModSecurity 3.0.0 has XSS via an onerror attribute of an IMG element. owasp · modsecurity 2018-07-03 high7.8 CVE-2018-12036 Path Traversal in OWASP Dependency-Check maven · org.owasp:dependency-check-maven 2018-06-07 medium6.1 CVE-2017-1000109 Persistent XSS vulnerability in Jenkins OWASP Dependency-Check Plugin maven · org.jenkins-ci.plugins:dependency-check-jenkins-plugin 2017-10-05 medium6.1 CVE-2017-14735 OWASP AntiSamy Cross-site Scripting vulnerability maven · org.owasp.antisamy:antisamy 2017-09-25

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.