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

Aperta
#38,625 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
66/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
java

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Java
Stelle
972
Fork
493
Merge medio
2g 12h
PR unite (30g)
228

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di dotCMS/core

Tutte le issue di dotCMS/core

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.