
CVE-2023-49238
https://notcve.org/view.php?id=CVE-2023-49238
09 Jan 2024 — 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 login, it is possible that an attacker logs in before the legitimate administrator logs in. En Gradle Enterprise anterior a 2023.1, un atacante remoto podría obtener acceso a una nueva instalación (en ciertos escenarios de instalación) debido a una contraseña de us... • https://security.gradle.com • CWE-521: Weak Password Requirements •

CVE-2022-41574
https://notcve.org/view.php?id=CVE-2022-41574
07 Oct 2022 — 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 access to an accidentally exposed internal endpoint. This is fixed in 2022.3.2. Una vulnerabilidad de control de acceso en Gradle Enterprise versiones 2022.4 hasta 2022.3.1 permite a atacantes remotos evitar que sean realizadas copias de seguridad y enviar corr... • https://security.gradle.com • CWE-863: Incorrect Authorization •

CVE-2022-27919
https://notcve.org/view.php?id=CVE-2022-27919
25 Mar 2022 — 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. Gradle Enterprise versiones anteriores a 2022.1, permite una ejecución de código remota si el proceso de instalación no especificó un archivo de configuración inicial. La configuración permite determinados accesos anónimos a la administración y a una API • https://security.gradle.com/advisory/2022-05 • CWE-276: Incorrect Default Permissions •

CVE-2022-25364
https://notcve.org/view.php?id=CVE-2022-25364
17 Mar 2022 — 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 manipulated entries that execute malicious code as part of a build. As of 2021.4.2, the built-in build cache is inaccessible-by-default, requiring explicit configuration of its access-control settings before it can be used. (Remote build cache nodes are unaffected as t... • https://security.gradle.com • CWE-276: Incorrect Default Permissions •

CVE-2022-27225
https://notcve.org/view.php?id=CVE-2022-27225
16 Mar 2022 — 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 functionality. For backwards compatibility with older Safari versions, Keycloak sets a duplicate of the cookie without the Secure attribute, which allows the cookie to be sent when accessing the location that cookie is set for via HTTP. This creates the potential for an att... • https://security.gradle.com/advisory/2022-03 • CWE-311: Missing Encryption of Sensitive Data •

CVE-2021-41589
https://notcve.org/view.php?id=CVE-2021-41589
27 Oct 2021 — 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 build cache node with its default configuration. This configuration allows anonymous access to the configuration user interface and anonymous write access to the build cache. If access control to the build cache is not changed from the default open configuration, a malicious actor with network access can populate the cache with manipulated entries th... • https://security.gradle.com • CWE-732: Incorrect Permission Assignment for Critical Resource •

CVE-2021-41619
https://notcve.org/view.php?id=CVE-2021-41619
27 Oct 2021 — 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 Java Virtual Machine startup options. Some of these options, such as -XX:OnOutOfMemoryError, allow specifying a command to be run on the host. This can be abused to run arbitrary commands on the host, should an attacker gain administrative access to the applicat... • https://security.gradle.com • CWE-94: Improper Control of Generation of Code ('Code Injection') •

CVE-2021-41590
https://notcve.org/view.php?id=CVE-2021-41590
27 Oct 2021 — 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. This test function can be used to identify the listening TCP ports available to the server, revealing information about the internal network environment. En Gradle Enterprise versiones hasta 2021.3, el sondeo del entorno de red del lado del servidor puede ocur... • https://security.gradle.com •

CVE-2020-15773
https://notcve.org/view.php?id=CVE-2020-15773
18 Sep 2020 — An issue was discovered in Gradle Enterprise before 2020.2.4. Because of unrestricted cross-origin requests to read-only data in the Export API, an attacker can access data as a user (for the duration of the browser session) after previously explicitly authenticating with the API. Se detectó un problema en Gradle Enterprise versiones anteriores a 2020.2.4. Debido a unas peticiones de origen cruzado no restringidas para datos de solo lectura en la API Export, un atacante puede acceder a los datos como u... • https://github.com/gradle/gradle/security/advisories • CWE-346: Origin Validation Error •

CVE-2020-15767
https://notcve.org/view.php?id=CVE-2020-15767
18 Sep 2020 — An issue was discovered in Gradle Enterprise before 2020.2.5. The cookie used to convey the CSRF prevention token is not annotated with the “secure” attribute, which allows an attacker with the ability to MITM plain HTTP requests to obtain it, if the user mistakenly uses a HTTP instead of HTTPS address to access the server. This cookie value could then be used to perform CSRF. Se detectó un problema en Gradle Enterprise versiones anteriores a 2020.2.5. La cookie utilizada para transmitir el token de prevenc... • https://github.com/gradle/gradle/security/advisories • CWE-311: Missing Encryption of Sensitive Data •