Gradle

Enterprise

23 vulnerabilities found.

Hinweis: Diese Liste kann unvollständig sein. Daten werden ohne Gewähr im Ursprungsformat bereitgestellt.
  • EPSS 0.03%
  • Published 26.01.2025 07:15:08
  • Last modified 26.01.2025 07:15:08

Develocity (formerly Gradle Enterprise) before 2024.1.8 has Incorrect Access Control. Project-level access control configuration was introduced in Enterprise Config schema version 8. Migration functionality from schema version 8 to versions 9 and 10 ...

  • EPSS 0.03%
  • Published 26.01.2025 06:15:23
  • Last modified 26.01.2025 07:15:09

Develocity (formerly Gradle Enterprise) before 2024.3.1 allows an attacker who has network access to a Develocity server to obtain the hashed password of the system user. The hash algorithm used by Develocity was chosen according to best practices fo...

  • EPSS 0.82%
  • Published 09.01.2024 02:15:44
  • Last modified 17.06.2025 16:15:25

In Gradle Enterprise before 2023.1, a remote attacker may be able to gain access to a new installation (in certain installation scenarios) because of a non-unique initial system user password. Although this password must be changed upon the first log...

  • EPSS 0.2%
  • Published 21.10.2022 12:15:11
  • Last modified 07.05.2025 15:15:55

A credential-exposure vulnerability in the support-bundle mechanism in Gradle Enterprise 2022.3 through 2022.3.3 allows remote attackers to access a subset of application data (e.g., cleartext credentials). This is fixed in 2022.3.3.

  • EPSS 0.18%
  • Published 07.10.2022 21:15:12
  • Last modified 21.11.2024 07:23:25

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 arbitrary text content to the configured installation-administrator contact address, via HTTP...

  • EPSS 2.15%
  • Published 25.03.2022 20:15:09
  • Last modified 21.11.2024 06:56:28

Gradle Enterprise before 2022.1 allows remote code execution if the installation process did not specify an initial configuration file. The configuration allows certain anonymous access to administration and an API.

  • EPSS 0.3%
  • Published 17.03.2022 17:15:07
  • Last modified 21.11.2024 06:52:04

In Gradle Enterprise before 2021.4.2, the default built-in build cache configuration allowed anonymous write access. If this was not manually changed, a malicious actor with network access to the build cache could potentially populate it with manipul...

  • EPSS 0.19%
  • Published 16.03.2022 01:15:08
  • Last modified 21.11.2024 06:55:26

Gradle Enterprise before 2021.4.3 relies on cleartext data transmission in some situations. It uses Keycloak for identity management services. During the sign-in process, Keycloak sets browser cookies that effectively provide remember-me functionalit...

  • EPSS 2.28%
  • Published 27.10.2021 14:15:07
  • Last modified 21.11.2024 06:26:32

An issue was discovered in Gradle Enterprise before 2021.1.2. There is potential remote code execution via the application startup configuration. The installation configuration user interface (available to administrators) allows specifying arbitrary ...

  • EPSS 0.21%
  • Published 27.10.2021 14:15:07
  • Last modified 21.11.2024 06:26:29

In Gradle Enterprise through 2021.3, probing of the server-side network environment can occur via an SMTP configuration test. The installation configuration user interface available to administrators allows testing the configured SMTP server settings...