Silverstripe Framework: Members with no password can be created and bypass custom login forms
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 for this purpose.
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 from Silverstripe and Christian Bünte
Czego dotyczy
Kliknij technologię, aby zobaczyć wszystkie dotyczące jej podatności.
| Platforma | Paczka | Podatne wersje | Poprawka w wersji |
|---|---|---|---|
| Paczka Composer | silverstripe/framework | >= 3.0.0, < 4.13.14, >= 5.0.0, < 5.0.13 | 4.13.14, 5.0.13 |
Odnośniki
- https://github.com/silverstripe/silverstripe-framework/security/advisories/GHSA-36xx-7vf6-7mv3
- https://nvd.nist.gov/vuln/detail/CVE-2023-32302
- https://github.com/github/advisory-database/pull/2575
- https://github.com/silverstripe/silverstripe-framework/commit/7b21b38ac4532d06565dfcefad50540ebd2b50f4
- https://github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/CVE-2023-32302.yaml
- https://github.com/silverstripe/silverstripe-framework
- https://github.com/silverstripe/silverstripe-framework/releases/tag/4.13.14
- https://github.com/silverstripe/silverstripe-framework/releases/tag/5.0.13
- https://www.silverstripe.org/download/security-releases/CVE-2023-32302
- Wektor CVSS
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:N- Słabość (CWE)
CWE-20, CWE-862- Platforma
- Composer
- Paczka
silverstripe/framework- Ujawniono
- 31.07.2023
- Aktualizacja
- 11.10.2026 10:22
Źródła i licencje
OSV / GitHub Advisory Database - GHSA-36xx-7vf6-7mv3 - CC BY 4.0
Historia podatności: silverstripe/framework
Wszystkie opisane podatności tej paczki (Paczka Composer), od najnowszej. Widać, czy to jednorazowa wpadka, czy paczka, której trzeba pilnować.
- Wszystkich wpisów
- 93
- Pierwsza → ostatnia
- 11.2019 08.2026
- Bez poprawki
- 1
- Wykorzystywana w atakach
- 0
Rozkład istotności
- Krytyczna 3
- Wysoka 13
- Średnia 69
- Niska 8
Ujawnienia w latach
- 2019: 5
- 2020: 2
- 2021: 0
- 2022: 23
- 2023: 3
- 2024: 53
- 2025: 6
- 2026: 1
-
Silverstripe Framework: Members with no password can be created and bypass custom login forms ten wpis
Dowiedz się, które podatności dotyczą Twojej aplikacji
Po podłączeniu integracji DockRay i włączeniu raportowania oprogramowania DockRay porównuje zgłoszone wersje komponentów ze znanymi podatnościami i powiadamia o potwierdzonych dopasowaniach. Zakres zależy od obsługiwanej technologii i dostępnych biuletynów.