GHSA-5r8w-66hq-rc39 silverstripe/framework's pre-existing alc_enc cookies log users in if remember me is disabled
Not scored
Published
Check this codebase for GHSA-5r8w-66hq-rc39 and fix it if it is affected.
What it is: GHSA-5r8w-66hq-rc39 is an authentication bypass vulnerability in silverstripe/framework, published on 27 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-5r8w-66hq-rc39 in the wild and no public exploit code.
Affected packages and fixed versions:
- silverstripe/framework (Packagist): affected from 3.1.19-rc1; fixed in 3.1.20
- silverstripe/framework (Packagist): affected from 3.1.19-rc1; fixed in 3.1.20
- silverstripe/framework (Packagist): affected from 3.2.4-rc1; fixed in 3.2.5
- silverstripe/framework (Packagist): affected from 3.2.4-rc1; fixed in 3.2.5
- silverstripe/framework (Packagist): affected from 3.3.2-rc1; fixed in 3.3.3
- silverstripe/framework (Packagist): affected from 3.3.2-rc1; fixed in 3.3.3
- silverstripe/framework (Packagist): affected from 3.4.0-rc1; fixed in 3.4.1
- silverstripe/framework (Packagist): affected from 3.4.0-rc1; fixed in 3.4.1
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/GHSA-5r8w-66hq-rc39/ (Markdown: https://insights.sbomify.com/GHSA-5r8w-66hq-rc39/index.md)
Attackers can hijack user sessions using pre-existing cookies if the remember-me feature is disabled after being enabled.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-5r8w-66hq-rc39?
GHSA-5r8w-66hq-rc39 is an authentication bypass vulnerability in silverstripe/framework, published on 27 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
If remember me is on and users log in with the box checked, if the developer then disabled "remember me" function, any pre-existing cookies will continue to authenticate users.
Which versions are affected by GHSA-5r8w-66hq-rc39?
8 open source packages ship an affected version, including silverstripe/framework.
| Package | Affected | Fixed in |
|---|---|---|
silverstripe/framework Packagist | From 3.1.19-rc1 | 3.1.20 |
silverstripe/framework Packagist | From 3.1.19-rc1 | 3.1.20 |
silverstripe/framework Packagist | From 3.2.4-rc1 | 3.2.5 |
silverstripe/framework Packagist | From 3.2.4-rc1 | 3.2.5 |
silverstripe/framework Packagist | From 3.3.2-rc1 | 3.3.3 |
silverstripe/framework Packagist | From 3.3.2-rc1 | 3.3.3 |
2 more packages
silverstripe/framework Packagist | From 3.4.0-rc1 | 3.4.1 |
silverstripe/framework Packagist | From 3.4.0-rc1 | 3.4.1 |
How do I fix GHSA-5r8w-66hq-rc39?
Upgrade silverstripe/framework to a fixed version for your release line: 3.1.20, 3.2.5, 3.3.3 or 3.4.1.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is GHSA-5r8w-66hq-rc39 being exploited?
There is no known exploitation of GHSA-5r8w-66hq-rc39 in the wild and no public exploit code.