fix(deps): update dependency org.assertj:assertj-core to v3.27.7 [security]

[alaudaa-renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
org.assertj:assertj-core (source)	3.26.3 -> 3.27.7

---

AssertJ has XML External Entity (XXE) vulnerability when parsing untrusted XML via isXmlEqualTo assertion

CVE-2026-24400 / GHSA-rqfh-9r24-8c9r

More information

Details

An XML External Entity (XXE) vulnerability exists in org.assertj.core.util.xml.XmlStringPrettyFormatter: the toXmlDocument(String) method initializes DocumentBuilderFactory with default settings, without disabling DTDs or external entities. This formatter is used by the isXmlEqualTo(CharSequence) assertion for CharSequence values.

An application is vulnerable only when it uses untrusted XML input with one of the following methods:

• isXmlEqualTo(CharSequence) from org.assertj.core.api.AbstractCharSequenceAssert
• xmlPrettyFormat(String) from org.assertj.core.util.xml.XmlStringPrettyFormatter

Impact

If untrusted XML input is processed by the methods mentioned above (e.g., in test environments handling external fixture files), an attacker could:

• Read arbitrary local files via file:// URIs (e.g., /etc/passwd, application configuration files)
• Perform Server-Side Request Forgery (SSRF) via HTTP/HTTPS URIs
• Cause Denial of Service via "Billion Laughs" entity expansion attacks

Mitigation

isXmlEqualTo(CharSequence) has been deprecated in favor of XMLUnit in version 3.18.0 and will be removed in version 4.0. Users of affected versions should, in order of preference:

1. Replace isXmlEqualTo(CharSequence) with XMLUnit, or
2. Upgrade to version 3.27.7, or
3. Avoid using isXmlEqualTo(CharSequence) or XmlStringPrettyFormatter with untrusted input.

XmlStringPrettyFormatter has historically been considered a utility for isXmlEqualTo(CharSequence) rather than a feature for AssertJ users, so it is deprecated in version 3.27.7 and removed in version 4.0, with no replacement.

References

• CWE-611: Improper Restriction of XML External Entity Reference
• OWASP XXE Prevention Cheat Sheet

Severity

• CVSS Score: Unknown
• Vector String: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:L/SC:H/SI:N/SA:N

References

• https://github.com/assertj/assertj/security/advisories/GHSA-rqfh-9r24-8c9r
• https://nvd.nist.gov/vuln/detail/CVE-2026-24400
• https://github.com/assertj/assertj/commit/85ca7eb6609bb179c043b85ae7d290523b1ba79a
• https://cheatsheetseries.owasp.org/cheatsheets/XML_External_Entity_Prevention_Cheat_Sheet.html
• https://github.com/assertj/assertj
• https://github.com/assertj/assertj/releases/tag/assertj-build-3.27.7

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Configuration

📅 Schedule: Branch creation - "" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[alaudabot]

🚨 Stale Pull Request Warning

This pull request has been inactive for 33 days.

Automated Actions Schedule:

• ⚠️ Warning: After 30 days (now)
• 🔒 Auto-close: After 60 days
• 🗑️ Branch deletion: After 90 days (if not protected)

To keep this PR active:

• Add new commits
• Reply to this comment
• Request reviews

Protected branches (won't be deleted): main,release-*,alauda-*

This is an automated message. Reply to this comment to reset the inactivity timer.

[alaudabot]

🚨 Stale Pull Request Warning

This pull request has been inactive for 35 days.

Automated Actions Schedule:

• ⚠️ Warning: After 30 days (now)
• 🔒 Auto-close: After 60 days
• 🗑️ Branch deletion: After 90 days (if not protected)

To keep this PR active:

• Add new commits
• Reply to this comment
• Request reviews

Protected branches (won't be deleted): main,release-*,alauda-*

This is an automated message. Reply to this comment to reset the inactivity timer.

[danielfbm]

PR Assist Bot — Owner Approval Needed

This PR targets release branch alauda-2025.1.0. Per policy, release-branch merges require explicit owner approval before the bot proceeds.

PR: AlaudaDevops/docker-sonarqube#35
Branch: alauda-2025.1.0
Type: Security / Dependency update (Renovate)

Please reply with /approve-merge or provide explicit approval for the bot to merge this PR on the next sweep.

[alaudabot]

[pr-assist-bot] Release Branch Security PR — Owner Approval Needed

This PR targets release branch alauda-2025.1.0. Per policy, release-branch dependency merges require explicit owner approval before the bot proceeds.

PR: #35 — fix(deps): update dependency org.assertj:assertj-core to v3.27.7 [security]
Branch: alauda-2025.1.0
Type: Security / Dependency update (Renovate)

Please reply with /approve-merge or provide explicit approval for the bot to merge this PR on the next sweep.

[alaudabot]

/retest

[alaudabot]

/retest

[alaudabot]

/retest

[alaudabot]

PR Assist Bot Analysis

Failure Type: Infrastructure / Repository Access
Failed Checks: sonarqube-build, sonarqube-plugin
Root Cause: The git-clone task is failing at the start of both pipelines (Tasks Completed: 1 Failed, Skipped: 10), preventing all downstream steps from running. This is a persistent clone failure on the alauda-2025.1.0 branch — possibly a credential, access, or branch configuration issue.
Retest attempts: 3 — stopping (same git-clone failure pattern, no progress)
Recommendation: Manual investigation needed — verify repository access for the CI runner to the alauda-2025.1.0 branch. The assertj-core v3.27.7 update itself may be fine; the CI infrastructure needs attention.

[danielfbm]

PR Assist Bot Analysis

Failure Type: Infrastructure/Transient (git-clone network timeout)
Failed Checks: Pipelines as Code CI / sonarqube-build, Pipelines as Code CI / sonarqube-plugin
Retest attempts: 3 — stopping (same failure pattern, no progress)

Root Cause: Both checks fail at the git-clone step with a 10-minute timeout — the TCP connection to GitHub never completed (consistent with a GitHub network connectivity window on the build cluster from ~2026-04-21T04:51 UTC). The assertj-core security update in this PR is unrelated.

Recommendation: Manual investigation needed — 3 retest attempts exhausted with the same network timeout. The build cluster's GitHub connectivity should be investigated. Other docker-sonarqube PRs (#29, #31, #32, #34) targeting the same branch have fully passing CI and may be merged once owner approval is given.

[alaudabot]

🚨 Stale Pull Request Warning

This pull request has been inactive for 32 days.

Automated Actions Schedule:

• ⚠️ Warning: After 30 days (now)
• 🔒 Auto-close: After 60 days
• 🗑️ Branch deletion: After 90 days (if not protected)

To keep this PR active:

• Add new commits
• Reply to this comment
• Request reviews

Protected branches (won't be deleted): main,release-*,alauda-*

This is an automated message. Reply to this comment to reset the inactivity timer.

[alaudabot]

🚨 Stale Pull Request Warning

This pull request has been inactive for 35 days.

Automated Actions Schedule:

• ⚠️ Warning: After 30 days (now)
• 🔒 Auto-close: After 60 days
• 🗑️ Branch deletion: After 90 days (if not protected)

To keep this PR active:

• Add new commits
• Reply to this comment
• Request reviews

Protected branches (won't be deleted): main,release-*,alauda-*

This is an automated message. Reply to this comment to reset the inactivity timer.