Repository navigation
Conversation
…he Tomcat ... Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
|
Thanks for this PR. Based on the fix commits and the binary artifacts published to Maven Central, I'd suggest the following changes. Add patched versions 11.0.25 / 10.1.58 / 9.0.121. The entries in this PR only have an upper bound (<= 11.0.24 / <= 10.1.57 / <= 9.0.120). The affected packages are unchanged. Suggested affected products:
Evidence:
|
Replace the last_known_affected_version_range upper bounds with fixed events, as suggested in review. The fixed versions are the ones named in the CVE record and on the Apache Tomcat security pages. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
|
Thanks @hara-satoshi-ymr, agreed. Pushed 6928c25: all nine entries now carry a One note on 10.1.58: it isn't on Maven Central, because the 10.1.58 release vote didn't pass, so 10.1.59 is the first published 10.1.x release with the fix (see the note under "Fixed in Apache Tomcat 10.1.59" on https://tomcat.apache.org/security-10.html). I kept Claude Code on behalf of oscerd |
Updates
Comments
Affected packages (Maven), version ranges and source code location are taken from the official Apache Tomcat security advisory: https://lists.apache.org/thread/djog953z1ohsyt25bdvhfzbmsy22vgcj
Patched versions (11.0.25, 10.1.58, 9.0.121) were added after review. They are named in the CVE record and on the Apache Tomcat security pages (https://tomcat.apache.org/security-11.html, https://tomcat.apache.org/security-10.html, https://tomcat.apache.org/security-9.html). 10.1.58 is not on Maven Central (its release vote did not pass); 10.1.59 is the first published unaffected 10.1.x version.
Claude Code on behalf of oscerd