// For flags

CVE-2022-23630

Dependency verification bypass in Gradle

Severity Score

7.5
*CVSS v3.1

Exploit Likelihood

*EPSS

Affected Versions

*CPE

Public Exploits

0
*Multiple Sources

Exploited in Wild

-
*KEV

Decision

-
*SSVC
Descriptions

Gradle is a build tool with a focus on build automation and support for multi-language development. In some cases, Gradle may skip that verification and accept a dependency that would otherwise fail the build as an untrusted external artifact. This occurs when dependency verification is disabled on one or more configurations and those configurations have common dependencies with other configurations that have dependency verification enabled. If the configuration that has dependency verification disabled is resolved first, Gradle does not verify the common dependencies for the configuration that has dependency verification enabled. Gradle 7.4 fixes that issue by validating artifacts at least once if they are present in a resolved configuration that has dependency verification active. For users who cannot update either do not use `ResolutionStrategy.disableDependencyVerification()` and do not use plugins that use that method to disable dependency verification for a single configuration or make sure resolution of configuration that disable that feature do not happen in builds that resolve configuration where the feature is enabled.

Gradle es una herramienta de compilación con un enfoque en la automatización de la compilación y el soporte para el desarrollo multilingüe. En algunos casos, Gradle puede omitir esa verificación y aceptar una dependencia que de otra manera fallaría la construcción como un artefacto externo no confiable. Esto ocurre cuando la verificación de dependencias está deshabilitada en una o más configuraciones y esas configuraciones presentan dependencias comunes con otras configuraciones que presentan la verificación de dependencias habilitada. Si la configuración que presenta deshabilitada la verificación de dependencias se resuelve primero, Gradle no verifica las dependencias comunes para la configuración que presenta habilitada la verificación de dependencias. Gradle versión 7.4 corrige este problema al comprobar los artefactos al menos una vez si están presentes en una configuración resuelta que presenta activa la verificación de dependencias. Para usuarios que no puedan actualizar, o bien no usen "ResolutionStrategy.disableDependencyVerification()" y no usen plugins que usen ese método para deshabilitar la verificación de dependencias para una única configuración, o bien asegúrense de que la resolución de la configuración que deshabilita esa característica no sea producida en las compilaciones que resuelven la configuración donde la característica está habilitada

*Credits: N/A
CVSS Scores
Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Attack Vector
Network
Attack Complexity
Medium
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial
* Common Vulnerability Scoring System
SSVC
  • Decision:-
Exploitation
-
Automatable
-
Tech. Impact
-
* Organization's Worst-case Scenario
Timeline
  • 2022-01-19 CVE Reserved
  • 2022-02-10 CVE Published
  • 2023-10-02 EPSS Updated
  • 2024-08-03 CVE Updated
  • ---------- Exploited in Wild
  • ---------- KEV Due Date
  • ---------- First Exploit
CWE
  • CWE-829: Inclusion of Functionality from Untrusted Control Sphere
CAPEC
Affected Vendors, Products, and Versions
Vendor Product Version Other Status
Vendor Product Version Other Status <-- --> Vendor Product Version Other Status
Gradle
Search vendor "Gradle"
Gradle
Search vendor "Gradle" for product "Gradle"
>= 6.2.0 <= 7.3.3
Search vendor "Gradle" for product "Gradle" and version " >= 6.2.0 <= 7.3.3"
-
Affected