mykola/freebsd-ports
1
0
Fork 0
forked from Lainports/freebsd-ports
Code Pull requests Activity

security/vuxml: Document www/py-social-auth-app-django vulnerability

Browse source
This commit is contained in:
Kai Knoblich 2024-04-28 09:04:00 +02:00
parent 8a25bceb3f
commit 3b46eb72e1
1 changed files with 28 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
security/vuxml/vuln/2024.xml
View file

@ -1,3 +1,31 @@
<vuln vid="b3affee8-04d1-11ef-8928-901b0ef714d4">
<topic>py-social-auth-app-django -- Improper Handling of Case Sensitivity</topic>
<affects>
<package>
<name>py38-social-auth-app-django</name>
<name>py39-social-auth-app-django</name>
<name>py310-social-auth-app-django</name>
<name>py311-social-auth-app-django</name>
<range><lt>5.4.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2024-32879">
<p>Python Social Auth is a social authentication/registration mechanism. Prior to version 5.4.1, due to default case-insensitive collation in MySQL or MariaDB databases, third-party authentication user IDs are not case-sensitive and could cause different IDs to match. This issue has been addressed by a fix released in version 5.4.1. An immediate workaround would be to change collation of the affected field.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2024-32879</cvename>
<url>https://github.com/python-social-auth/social-app-django/security/advisories/GHSA-2gr8-3wc7-xhj3</url>
</references>
<dates>
<discovery>2024-04-24</discovery>
<entry>2024-04-28</entry>
</dates>
</vuln>
<vuln vid="7a42852d-0347-11ef-9f97-a8a1599412c6">
<topic>chromium -- multiple security fixes</topic>
<affects>