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

未关闭
#38,625 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
66/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
java

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Java
星标
972
派生
493
平均合并
2 天 12 小时
30 天内合并 PR
228

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

dotCMS/core 的其他 Issue

查看 dotCMS/core 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。