Skip to content

USPR-13775: bump netty resolutionStrategy floor to 4.2.16.Final - #385

Merged
catarina-correia merged 2 commits into
mainfrom
claude/USPR-13775-netty-4.2.16-security-fix
Jul 31, 2026
Merged

USPR-13775: bump netty resolutionStrategy floor to 4.2.16.Final#385
catarina-correia merged 2 commits into
mainfrom
claude/USPR-13775-netty-4.2.16-security-fix

Conversation

@midnight-clue

@midnight-clue midnight-clue Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Context & Problem

Dependabot security alert #106 on openapi-validation-java flags io.netty:netty-codec-http versions 4.2.0.Final-4.2.15.Final as vulnerable to a zlib header block decompression bomb issue (GHSA-mvh2-crg5-v77c, high severity), patched in 4.2.16.Final. The repo's root build.gradle pins/enforces netty at exactly 4.2.15.Final via a resolutionStrategy.eachDependency block (added for earlier, unrelated CVEs), which is now itself within the newly disclosed vulnerable range. USPR-13775

Solution

Bumped the enforced io.netty floor in the root build.gradle resolutionStrategy.eachDependency block from 4.2.15.Final to 4.2.16.Final, and extended the existing because(...) advisory comment to add GHSA-mvh2-crg5-v77c while keeping all previously-listed GHSA references (multiple prior Netty CVEs already fixed by 4.2.15.Final).

Note: beyond the literal build.gradle change described in the ticket, I also bumped the two ext['netty.version'] = '4.2.15.Final' overrides in examples/example-spring-boot-starter-web/build.gradle and examples/example-spring-boot-starter-webflux/build.gradle to 4.2.16.Final. These are Spring Dependency Management BOM overrides that pin netty independently of the root resolutionStrategy; the prior USPR-13707 commit (850a009) updated both the resolutionStrategy and these two example overrides together when the netty floor last moved, so leaving them at 4.2.15.Final here would have left the examples still vulnerable. This follows that established pattern.

Verification

  • io.netty resolutionStrategy floor raised to 4.2.16.Final in root build.gradle, netty-codec-http no longer resolves within the GHSA-mvh2-crg5-v77c vulnerable range (4.2.0.Final-4.2.15.Final) (manual review of build.gradle + gradle dependency resolution check)
  • because() comment updated to reference GHSA-mvh2-crg5-v77c alongside existing advisories (manual review)
  • Verified no other location in the repo pins io.netty below 4.2.16.Final; found and updated the two example ext['netty.version'] overrides to match (repo-wide grep for "netty")

🔍 Braintrust trace

claude and others added 2 commits July 30, 2026 15:57
USPR-13775: Fix GHSA-mvh2-crg5-v77c (io.netty:netty-codec-http zlib header
block decompression bomb). Bump the enforced netty floor version in root
build.gradle from 4.2.15.Final to 4.2.16.Final. Updated the because()
advisory comment to include GHSA-mvh2-crg5-v77c while retaining all
previously-listed CVE references.

Co-Authored-By: Catarina Correia <catarina.correia@getyourguide.com>
Update Spring Dependency Management BOM overrides in both example
subprojects (example-spring-boot-starter-web and
example-spring-boot-starter-webflux) to use netty 4.2.16.Final, matching
the bump to the root resolutionStrategy floor. This ensures examples
remain consistent with the enforced netty version and are not vulnerable
to GHSA-mvh2-crg5-v77c.

Co-Authored-By: Catarina Correia <catarina.correia@getyourguide.com>
@midnight-clue
midnight-clue Bot marked this pull request as ready for review July 30, 2026 16:02
@midnight-clue
midnight-clue Bot requested a review from a team as a code owner July 30, 2026 16:02
@gyg-pr-tool
gyg-pr-tool Bot requested a review from catarina-correia July 30, 2026 16:03
@catarina-correia
catarina-correia merged commit 4304d56 into main Jul 31, 2026
4 checks passed
@catarina-correia
catarina-correia deleted the claude/USPR-13775-netty-4.2.16-security-fix branch July 31, 2026 07:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants