<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 14:00:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-32879 — social-auth-app-django Improper Handling of Case Sensitivity vulnerability</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-32879</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; python-social-auth social-app-django&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; python-social-auth social-app-django&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-32879</guid>
    </item>
    <item>
      <title>GHSA-2gr8-3wc7-xhj3 — social-auth-app-django affected by Improper Handling of Case Sensitivity</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2gr8-3wc7-xhj3</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: social-auth-app-django&lt;/p&gt;
&lt;p&gt;### Impact
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.&lt;/p&gt;
&lt;p&gt;### Patches
This issue has been addressed by https://github.com/python-social-auth/social-app-django/pull/566 and fix released in 5.4.1.&lt;/p&gt;
&lt;p&gt;### Workarounds
An immediate workaround would be to change collation of the affected field:&lt;/p&gt;
&lt;p&gt;```mysql
ALTER TABLE `social_auth_usersocialauth` MODIFY `uid` varchar(255) COLLATE `utf8_bin`;
```&lt;/p&gt;
&lt;p&gt;### References
This issue was discovered by folks at https://opencraft.com/.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: social-auth-app-django&lt;/p&gt;
&lt;p&gt;### Impact
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.&lt;/p&gt;
&lt;p&gt;### Patches
This issue has been addressed by https://github.com/python-social-auth/social-app-django/pull/566 and fix released in 5.4.1.&lt;/p&gt;
&lt;p&gt;### Workarounds
An immediate workaround would be to change collation of the affected field:&lt;/p&gt;
&lt;p&gt;```mysql
ALTER TABLE `social_auth_usersocialauth` MODIFY `uid` varchar(255) COLLATE `utf8_bin`;
```&lt;/p&gt;
&lt;p&gt;### References
This issue was discovered by folks at https://opencraft.com/.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2gr8-3wc7-xhj3</guid>
    </item>
  </channel>
</rss>
