social-auth-core has a Session Fixation issue

[ Description ]Official description

Python Social Auth is a social authentication/registration mechanism. Prior to version 5.0.0, the partial-pipeline resume mechanism accepted `partial_token` as a bearer credential without binding it to the browser session that created it. Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as `mail_validation` or custom steps decorated with `@partial`. The issue has been fixed in version 5.0.0 by binding partial pipeline resumes to the originating browser session.

[ Fixes ]Fixes and patches

• social-auth-core 5.0.0Fixed version · GitHub Advisories · pip package social-auth-core: upgrade to 5.0.0 or later (affected < 5.0.0)

[ Packages ]Affected open-source packages

• social-auth-core pipAffected < 5.0.0 · fixed in 5.0.0 · GHSA-vqg6-3fw6-j9jg

[ References ]References

• github.com/python-social-auth/social-core/security/advisories/GHSA-vqg6-3fw6-j9jg