Python Social Auth - Django has unsafe account association
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| python-social-auth | social-app-django | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Python-social-auth | Social-app-django | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-wv4w-6qv2-qqfg | Python Social Auth - Django has unsafe account association |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.542% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Python-social-auth
Python-social-auth social-app-django |
|
| Vendors & Products |
Python-social-auth
Python-social-auth social-app-django |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Python Social Auth is a social authentication/registration mechanism. In versions prior to 5.6.0, upon authentication, the user could be associated by e-mail even if the `associate_by_email` pipeline was not included. This could lead to account compromise when a third-party authentication service does not validate provided e-mail addresses or doesn't require unique e-mail addresses. Version 5.6.0 contains a patch. As a workaround, review the authentication service policy on e-mail addresses; many will not allow exploiting this vulnerability. | |
| Title | Python Social Auth - Django has unsafe account association | |
| Weaknesses | CWE-303 | |
| References |
|
|
| Metrics |
cvssV4_0
|