Skip to content
Fencer Intel
high —

GHSA-m4mf-rqrp-5pq8 json

HubSpot, Monzo and WLCG backends collapse all users onto uid "None", allowing any user of the same provider to authenticate as the first user's account

published last mo. modified last mo.

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository python-social-auth/social-core. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

Security advisory published by the maintainers of python-social-auth/social-core for social-auth-core: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.

Patch / fix

  • pypi social-auth-core 6.1.1

Is GHSA-m4mf-rqrp-5pq8 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
pypi social-auth-core
>=4.5.4, <=6.1.0
6.1.1

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of python-social-auth/social-core published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.