Skip to content

Update Tomcat, HttpCore5, Jackson for OWASP CVE remediation#1440

Merged
labkey-willm merged 1 commit into
release26.3-SNAPSHOTfrom
26.3_fb_owasp_cves
Jul 9, 2026
Merged

Update Tomcat, HttpCore5, Jackson for OWASP CVE remediation#1440
labkey-willm merged 1 commit into
release26.3-SNAPSHOTfrom
26.3_fb_owasp_cves

Conversation

@labkey-willm

Copy link
Copy Markdown
Contributor

Rationale

LabKey Server's OWASP Dependency Check build is failing on develop with 124 findings, the bulk of them from a handful of vulnerable third-party dependencies. This PR clears the findings that can be resolved by version bumps/forces and suppresses two verified false positives.

this is a backport from develop

Related Pull Requests

Changes

  • Tomcat 11.0.22 -> 11.0.23: CVE-2026-53434 and CVE-2026-55276 (CRITICAL 9.1), plus CVE-2026-53404, CVE-2026-55955, CVE-2026-55956, CVE-2026-50229
  • httpcore5 5.4.2 -> 5.4.3, and a new httpcore5-h2 force at 5.4.3 (previously transitive at 5.3.6): CVE-2026-54399
  • Jackson 2.21.4 -> 2.21.5 (jacksonVersion, jacksonDatabindVersion, jacksonJaxrsBaseVersion): CVE-2026-54515
  • Suppress classic httpcore 4.x for CVE-2026-54399 (the CVE is scoped to HttpComponents Core 5.x; the 4.x line is EOL and unaffected)
  • Suppress Kotlin runtime jars for CVE-2026-53914 (a Kotlin build-cache-metadata deserialization flaw scored 6.7 MEDIUM by JetBrains, not applicable to the shipped stdlib/reflect runtime jars)
  • Update comments to document that apacheTomcatVersion is intentionally held ahead of Spring Boot's managed Tomcat

@labkey-willm labkey-willm self-assigned this Jul 8, 2026
@labkey-willm labkey-willm requested a review from labkey-adam July 8, 2026 23:21
@labkey-willm labkey-willm merged commit df46309 into release26.3-SNAPSHOT Jul 9, 2026
9 of 10 checks passed
@labkey-willm labkey-willm deleted the 26.3_fb_owasp_cves branch July 9, 2026 17:00
labkey-willm added a commit that referenced this pull request Jul 10, 2026
…sitive (#1441)

## Rationale
OWASP dependency-check flagged CVE-2026-54399 (HTTP/1.1 parser DoS) and
CVE-2026-54428 (HTTP/2 HPACK decoder DoS), both scoped to Apache
HttpComponents Core "up to and including 5.4.2". Two things were needed:
the classic httpcore 4.x artifact is not affected (4.x has no HTTP/2
module and no fixed 4.4.x release exists for these 5.x-scoped CVEs), so
it is suppressed as a false positive; and the real exposure is
httpcore5-h2, which was resolving transitively to 5.3.6 because the
resolutionStrategy force block pinned httpcore5 and httpclient5 but not
httpcore5-h2.

## Related Pull Requests
- #1440

## Changes
- Force `org.apache.httpcomponents.core5:httpcore5-h2` to
`httpcore5Version` (5.4.3), upgrading the transitive 5.3.6 past the
vulnerable 5.4.2 ceiling and clearing both CVEs. Verified via
`:server:modules:platform:api:dependencies` (`5.3.6 -> 5.4.3`).
- Suppress false positive CVE-2026-54428 on the classic httpcore 4.x
artifact.

## Note on shaded copies
Shaded copies of these http5 libraries originate from labkey-api-jdbc
(`:remoteapi:labkey-api-jdbc`, only wired into the build under the `all`
settings/module set) and are being addressed separately. They do not
appear in a `-PmoduleSet=community` scan because that project is out of
scope there.

<!-- list of standard tasks (remove this comment to enable)
## Tasks 📍
- [ ] Claude Code Review
- [ ] Manual Testing
- [ ] Test Automation
- [ ] Verify Fix
-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants