NetSight

Security Dashboard

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

Reset
80 matching advisories · page 2 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2022-41574 An access-control vulnerability in Gradle Enterprise 2022.4 through 2022.3.1 allows remote attackers to prevent backups from occurring, and send emails with ar… gradle · enterprise 2022-10-07 high8.8 CVE-2022-26049 Goomph before 3.37.2 allows malicious zip file to write contents to arbitrary locations maven · com.diffplug.gradle:goomph 2022-09-11 medium6.6 CVE-2022-31156 Gradle is a build tool. gradle · gradle 2022-07-14 high7.5 CVE-2022-30587 Gradle Enterprise through 2022.2.2 has Incorrect Access Control that leads to information disclosure. gradle · gradle_enterprise 2022-06-06 high7.2 CVE-2022-30586 Gradle Enterprise through 2022.2.2 has Incorrect Access Control that leads to code execution. gradle · gradle 2022-06-06 critical9.8 CVE-2022-27919 Gradle Enterprise before 2022.1 allows remote code execution if the installation process did not specify an initial configuration file. gradle · enterprise 2022-03-25 high8.1 CVE-2022-25364 In Gradle Enterprise before 2021.4.2, the default built-in build cache configuration allowed anonymous write access. gradle · enterprise 2022-03-17 medium6.5 CVE-2022-27225 Gradle Enterprise before 2021.4.3 relies on cleartext data transmission in some situations. gradle · enterprise 2022-03-16 medium5.3 CVE-2022-24329 In JetBrains Kotlin before 1.6.0, it was not possible to lock dependencies for Multiplatform Gradle Projects. maven · org.jetbrains.kotlin:kotlin-stdlib 2022-02-25 high7.5 CVE-2022-23630 Gradle is a build tool with a focus on build automation and support for multi-language development. gradle · gradle 2022-02-10 high7.2 CVE-2021-41619 An issue was discovered in Gradle Enterprise before 2021.1.2. gradle · enterprise 2021-10-27 medium5.3 CVE-2021-41590 In Gradle Enterprise through 2021.3, probing of the server-side network environment can occur via an SMTP configuration test. gradle · enterprise 2021-10-27 critical9.8 CVE-2021-41589 In Gradle Enterprise before 2021.3 (and Enterprise Build Cache Node before 10.0), there is potential cache poisoning and remote code execution when running the… gradle · build_cache_node, gradle · enterprise 2021-10-27 medium6.1 CVE-2021-25959 Cross-site Scripting in OpenCRX maven · org.opencrx:opencrx-core, maven · org.opencrx:opencrx-core-models, maven · org.opencrx:opencrx-core-config +2 2021-09-29 high8.1 CVE-2021-41588 In Gradle Enterprise before 2021.1.3, a crafted request can trigger deserialization of arbitrary unsafe Java objects. gradle · gradle 2021-09-24 high7.5 CVE-2021-41587 In Gradle Enterprise before 2021.1.3, an attacker with the ability to perform SSRF attacks can potentially discover credentials for other resources. gradle · gradle 2021-09-24 high7.5 CVE-2021-41586 In Gradle Enterprise before 2021.1.3, an attacker with the ability to perform SSRF attacks can potentially reset the system user password. gradle · gradle 2021-09-24 high7.5 CVE-2021-41584 Gradle Enterprise before 2021.1.3 can allow unauthorized viewing of a response (information disclosure of possibly sensitive build/configuration details) via a… gradle · gradle 2021-09-24 high7.5 CVE-2021-32751 Gradle is a build tool with a focus on build automation. gradle · gradle 2021-07-20 high8.8 CVE-2021-29428 In Gradle before version 7.0, on Unix-like systems, the system temporary directory can be created with open permissions that allow multiple users to create and… gradle · gradle, quarkus · quarkus 2021-04-13 high8.0 CVE-2021-29427 In Gradle from version 5.1 and before version 7.0 there is a vulnerability which can lead to information disclosure and/or dependency poisoning. gradle · gradle, quarkus · quarkus 2021-04-13 medium4.0 CVE-2021-29429 In Gradle before version 7.0, files created with open permissions in the system temporary directory can allow an attacker to access information downloaded by G… gradle · gradle, quarkus · quarkus 2021-04-12 high7.4 CVE-2021-21361 Sensitive information disclosure via log in com.bmuschko:gradle-vagrant-plugin maven · com.bmuschko:gradle-vagrant-plugin 2021-03-09 medium6.5 CVE-2021-26719 A directory traversal issue was discovered in Gradle gradle-enterprise-test-distribution-agent before 1.3.2, test-distribution-gradle-plugin before 1.3.2, and … gradle · enterprise_test_distribution_agent, gradle · maven, gradle · test_distribution 2021-02-09 high7.5 CVE-2020-11979 Code injection in Apache Ant maven · org.apache.ant:ant 2020-10-01 medium6.5 CVE-2020-15773 An issue was discovered in Gradle Enterprise before 2020.2.4. gradle · enterprise 2020-09-18 high8.8 CVE-2020-15776 An issue was discovered in Gradle Enterprise 2018.2 - 2020.2.4. gradle · enterprise 2020-09-18 high7.5 CVE-2020-15775 An issue was discovered in Gradle Enterprise 2017.1 - 2020.2.4. gradle · enterprise 2020-09-18 medium6.8 CVE-2020-15774 An issue was discovered in Gradle Enterprise 2018.5 - 2020.2.4. gradle · enterprise 2020-09-18 medium4.9 CVE-2020-15772 An issue was discovered in Gradle Enterprise 2018.5 - 2020.2.4. gradle · enterprise 2020-09-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.