[GHSA-j39c-c8hj-x4j3] Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat#7618
Open
hara-satoshi-ymr wants to merge 1 commit intohara-satoshi-ymr/advisory-improvement-7618from
Conversation
github-actions
Bot
changed the base branch from
main
to
hara-satoshi-ymr/advisory-improvement-7618
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the GHSA-j39c-c8hj-x4j3 advisory’s Maven “affected” package coverage to better reflect where the vulnerable h2c upgrade handling code resides in Tomcat and to include milestone releases called out by the advisory text.
Changes:
- Adjusted
org.apache.tomcat.embed:tomcat-embed-coreintroduced versions to include affected milestone releases (10.0.0-M1,9.0.0.M1). - Added
org.apache.tomcat:tomcat-coyoteas an additional affected Maven package across the same supported version lines (10.0.x, 9.0.x, 8.5.x).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates
Comments
Two changes that belong together:
Adding
org.apache.tomcat:tomcat-coyoteto the affected products. The vulnerable code (h2c upgrade handling) lives in Coyote, so installations that shiptomcat-coyote— typically the standalone Tomcat distribution rather than the embedded one — are also affected even whentomcat-embed-coreis not present.Aligning the existing
org.apache.tomcat.embed:tomcat-embed-coreranges with the advisory text. The advisory states the vulnerability begins at10.0.0-M1and9.0.0.M1, but the existing ranges started at10.0.0and9.0.0, which silently excluded affected milestone releases. The 8.5.x range is left as-is because the advisory text starts at8.5.0(no milestone qualifier).The new tomcat-coyote ranges use the same milestone-aware introduced versions for consistency. (This re-submits #7523 / #7614 with the introduced versions corrected per Copilot's review.)