Â ÂJetty 9.2.9.v20150224
This release is considered a critical security release for all
users of Jetty 9.2.3 through 9.2.8.
Â + A critical security vulnerability has been fixed with how Jetty
Â Â reports 400 Invalid Character responses when the HttpParser
Â Â encounters an error.
Â Â This 400 response can contain information from past buffer
Â Â use from within Jetty.Â Revealing random buffer contents
Â Â from other previously handled requests.
For details see either the bug at
Or the markdown about the vulnerability at
Â Â ÂÂ
The artifacts are also available in the Global Central Repository.
Eclipse P2 repositories are available now.
If you find an issue with this release you can open a bug through the
guided bugzilla page located here:
Documentation can be found at our documentation hub
Finally, a reminder that both dev and prod support are offered through
or ping me directly if you are interested in learning more.
Documentation PDF's are available for direct download on the
The Jetty Development Team
jetty-9.2.9.v20150224 - 24 February 2015
Â+ 459273 Redundant license notices
Â+ 460176 When checking for precompiled jsp, ensure classname is present
Â+ 460180 Jaas demo has wrong doco in html
Â+ 460291 AsyncGzipFilter Mappings
Â+ 460371 AsyncMiddleManServlet.GZipContentTransformer fails if last transform
Â Âhas no output
Â+ 460372 if web.xml does not contain jspc maven plugin insertionMarker
Â Âbehavior is wrong
Â+ 460443 Race condition releasing the response buffer.
Â+ 460642 HttpParser error 400 can expose previous buffer contents in HTTP
Â Âstatus reason message