Bug 1830206

Summary: wildfly-elytron: session fixation variation when using Undertow FORM authentication
Product: [Other] Security Response Reporter: Ted Jongseok Won <jwon>
Component: vulnerabilityAssignee: Nobody <nobody>
Status: NEW --- QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: aileenc, akoufoud, alazarot, anstephe, asoldano, bbaranow, bmaxwell, boliveir, brian.stansberry, cdewolf, chazlett, darran.lofthouse, dkreling, dosoudil, eleandro, fjuma, gmalinko, ibek, iweiss, janstey, jawilson, jochrist, jpallich, jperkins, jrokos, jwon, kverlaen, kwills, lgao, mnovotny, msochure, msvehla, nwallace, pdelbell, pdrozd, pjindal, pmackay, rguimara, rstancel, rsvoboda, smaestri, sthorger, tom.jenkinson, yborgess
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in WildFly Elytron. A variation to the use of a session fixation exploit when using Undertow was found despite Undertow switching the session ID after authentication. The highest threat from this vulnerability is to data confidentiality and integrity.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1822718, 2018242    

Description Ted Jongseok Won 2020-05-01 05:29:50 UTC
A flaw was found in WildFly Elytron. Session fixation exploit where WildFly Elytron is in use has identified a possible variation to make use of a session fixation exploit when using Undertow despite Undertow switching the session ID AFTER authentication.

This exploit can be demonstrated with a default installation of JBoss EAP 7.2, 7.3 or WildFly.  This would also be applicable with older EAP releases including EAP 6. However, JWS 5.3, 3.1.8(tomcat7/tomcat8), and the latest Apache Tomcat 9.0.34 are not affected.