The core vulnerability stems from the HTTP client following redirects while retaining Authorization headers. The commit diff shows the fix involved adding authority comparison (originAuthority != url.authority) and subsequent removal of Authorization headers in HttpRedirect.kt. This confirms the vulnerable logic resided in the redirect handling code path prior to these checks being implemented. The handleCall() function is directly responsible for processing redirects and building subsequent requests, making it the clear location of the vulnerable behavior.