GHSA-36xx-7vf6-7mv3 json
Silverstripe Framework: Members with no password can be created and bypass custom login forms
published 3y ago modified 2y ago also CVE-2023-32302
- cvss
- 0.0
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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->isDefaultAdmin()) { return false; } // return true if a blank password is valid for this member $authenticator = new MemberAuthenticator(); return $authenticator->checkPassword($member, '')->isValid(); } ``` Once you have identified the records with empty passwords, it's up to you how to handle this. The most sensible way to resolve this is probably to generate a new secure password for each of these members, mark it as immediately expired, and email each affected member (assuming they have a valid email address in the system).
Users would need to opt-in to insecure behavior by using a configuration which allowed for empty passwords. These configurations are not expected and hence this advisory is primarily informational in nature.
Reported by: [Sabina Talipova](https://www.silverstripe.com/about-us/team/?member=sabina-talipova) from Silverstripe and [Christian Bünte](https://github.com/bimthebam)
Patch / fix
- packagist silverstripe/framework 4.13.14, 5.0.13
Is GHSA-36xx-7vf6-7mv3 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 FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 0.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | silverstripe/framework | >=3.0.0, <4.13.14 >=5.0.0, <5.0.13 |
4.13.14 5.0.13 |
Classification
References
-
github.com
/silverstripe/silverstripe-framework/commit/7b21b38ac4532d06565dfcefad50540ebd2b50f4
web
-
github.com
/silverstripe/silverstripe-framework/security/advisories/GHSA-36xx-7vf6-7mv3
web
-
nvd.nist.gov
/vuln/detail/CVE-2023-32302
advisory
-
github.com
/github/advisory-database/pull/2575
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/CVE-2023-32302.yaml
web
-
github.com
/silverstripe/silverstripe-framework
package
-
github.com
/silverstripe/silverstripe-framework/releases/tag/4.13.14
web
-
github.com
/silverstripe/silverstripe-framework/releases/tag/5.0.13
web
-
silverstripe.org
/download/security-releases/CVE-2023-32302
web
Sources
- GitHub Advisory GHSA-36xx-7vf6-7mv3
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.