https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 08:06:57 +0000 https://cve.radiocsirt.org/vuln/fkie_cve-2023-32302 <p>Rejected reason: Authoritative user requested CVE rejection https://github.com/github/advisory-database/pull/2575#issuecomment-1745811653</p> <p>Rejected reason: Authoritative user requested CVE rejection https://github.com/github/advisory-database/pull/2575#issuecomment-1745811653</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-32302 https://cve.radiocsirt.org/vuln/ghsa-36xx-7vf6-7mv3 <p><strong>Affected:</strong> Packagist: silverstripe/framework</p> <p>When a new `Member` record was created in the cms it was possible to set a blank password. If an attacker knows the email address of the user with the blank password then they can attempt to log in using an empty password. The default member authenticator, login form and basic auth all require a non-empty password, however if a custom authentication method is used it may allow a successful login with the empty password. Starting with this release, blank passwords are no no longer allowed when members are created in the CMS. Programatically created `Member` records, such as those used in unit tests, still allow blank passwords. You may have some `Member` records in your system already which have empty passwords. To detect these, you can loop over all `Member` records with `Member::get()` and pass each record into the below method. It might be sensible to create a [`BuildTask`](https://api.silverstripe.org/5/SilverStripe/Dev/BuildTask.html) for this purpose. ```php private function memberHasBlankPassword(Member $member): bool { // skip default admin as this is created programatically if ($member-&gt;isDefaultAdmin()) { return false; } // return true if a blank password is valid for this member $authenticator = new MemberAuthenticator(); return $authenticator-&gt;checkPassword($member, &#39;&#39;)-&gt;isValid(); } ``` Once you have identified the records with empty passwords, it&#39;s up to you how to handle this. The mos…</p> <p><strong>Affected:</strong> Packagist: silverstripe/framework</p> <p>When a new `Member` record was created in the cms it was possible to set a blank password. If an attacker knows the email address of the user with the blank password then they can attempt to log in using an empty password. The default member authenticator, login form and basic auth all require a non-empty password, however if a custom authentication method is used it may allow a successful login with the empty password. Starting with this release, blank passwords are no no longer allowed when members are created in the CMS. Programatically created `Member` records, such as those used in unit tests, still allow blank passwords. You may have some `Member` records in your system already which have empty passwords. To detect these, you can loop over all `Member` records with `Member::get()` and pass each record into the below method. It might be sensible to create a [`BuildTask`](https://api.silverstripe.org/5/SilverStripe/Dev/BuildTask.html) for this purpose. ```php private function memberHasBlankPassword(Member $member): bool { // skip default admin as this is created programatically if ($member-&gt;isDefaultAdmin()) { return false; } // return true if a blank password is valid for this member $authenticator = new MemberAuthenticator(); return $authenticator-&gt;checkPassword($member, &#39;&#39;)-&gt;isValid(); } ``` Once you have identified the records with empty passwords, it&#39;s up to you how to handle this. The mos…</p> https://cve.radiocsirt.org/vuln/ghsa-36xx-7vf6-7mv3 https://cve.radiocsirt.org/vuln/gsd-2023-32302 gsd-2023-32302 https://cve.radiocsirt.org/vuln/gsd-2023-32302