chore(deps): align guava in tools/dotcms-cli with the BOM (32.1.3 → 33.7.2)

Abierto
#38,625 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
66/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
java

Línea de trabajo

Read tools/dotcms-cli/pom.xml and the Quarkus BOM import, then run the provided dependency:list command to confirm the resolved Guava version. Add a dependencyManagement entry before the Quarkus BOM import to pin Guava to 33.7.2-jre or later. Verify the resolution, JVM build and tests, native profile build and binary, and the full module dependency tree.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

CVSS 4.0 : N/A Team : Security
Description

tools/dotcms-cli resolves com.google.guava:guava:32.1.3-jre, while the rest of the project moved to 33.7.2-jre in #38493 / #38603. The bump does not reach the CLI because the CLI module inherits dotcms-parent and never imports bom/application/pom.xml, where the new guava.version property lives. Its Guava comes instead from the Quarkus platform BOM (quarkus.platform.version 3.6.0, tools/dotcms-cli/pom.xml:24), pulled in transitively — tools/dotcms-cli/api-data-model/pom.xml:80-81 declares jackson-datatype-guava.

Reproduce with:

./mvnw dependency:list -f tools/dotcms-cli/pom.xml -Dincludes=com.google.guava:guava
[INFO]    com.google.guava:guava:jar:32.1.3-jre:compile

32.1.3-jre is inside the range covered by CVE-2026-102554 (GHSA-xxph-c9ww-hj94, affected <= 33.7.1). The CLI is a REST/JSON client and does not deserialize Java object streams from a remote source, so the deserialization path the advisory describes is not reachable there the way it is on the server; cicd_scheduled_image-cve-scan.yml also only scans the dotcms/dotcms images, not the CLI distribution. The reason to align it is that we publish the artifact and anyone scanning it will flag the version.

Quarkus itself does not need to be upgraded. Guava is not a platform artifact, so a dependencyManagement entry declared ahead of the Quarkus BOM import in tools/dotcms-cli/pom.xml pins it.

Acceptance Criteria
  • tools/dotcms-cli resolves guava 33.7.2-jre or later; the command above prints only that version
  • The CLI still builds and its tests pass on the JVM
  • The native profile still builds and the native binary runs — GraalVM is the place a library change shows up, through reflection and build-time initialization
  • Confirm nothing else in the module tree consumes Guava in a way the bump breaks (the full dependency:tree was not completed while filing this)
Additional Context

Found while QA-ing #38493. No change expected in CLI behavior; this is a version alignment.

Lenguaje dominante
Java
Estrellas
972
Forks
493
Merge medio
2 d 12 h
PR fusionados (30 d)
228

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de dotCMS/core

Todos los issues de dotCMS/core

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.