LowGHSA-f3wp-xpv2-6vmg

silverstripe/framework password encryption salt not updated

Published 27 May 2024 · Updated 2 Dec 2024

Affected packages

Affected
>=3.1.19-rc1 <3.1.20
Fixed in
3.1.20
Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.1.20
Affected
>=3.2.4-rc1 <3.2.5
Fixed in
3.2.5
Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.2.5
Affected
>=3.3.2-rc1 <3.3.3
Fixed in
3.3.3
Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.3.3
Affected
>=3.4.0-rc1 <3.4.1
Fixed in
3.4.1
Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.4.1

Details

When a user changes their password, the internal salt used for hashing their password is not updated.

Although this is not considered a security vulnerability, this behaviour has been improved to ensure the salt is reset on change of password.

Is GHSA-f3wp-xpv2-6vmg in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected silverstripe/framework, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.