# GHSA-4qx8-j9vh-2628: silverstripe/framework's User-Agent header not correctly invalidating user session

> Attackers can hijack user sessions because the framework fails to invalidate sessions when the User-Agent header changes.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2024

## What is GHSA-4qx8-j9vh-2628?

GHSA-4qx8-j9vh-2628 is a vulnerability in silverstripe/framework, published on 27 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security protection device in Session designed to protect session hijacking was not correctly functioning. This function intended to protect user sessions by detecting changes in the User-Agent header, but modifications to this header were not correctly invalidating the user session.

## Which versions are affected by GHSA-4qx8-j9vh-2628?

4 open source packages ship an affected version, including silverstripe/framework.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/framework` | Packagist | From 3.5.0-rc1 | 3.5.6 |
| `silverstripe/framework` | Packagist | From 3.5.0-rc1 | 3.5.6 |
| `silverstripe/framework` | Packagist | From 3.6.0-rc1 | 3.6.3 |
| `silverstripe/framework` | Packagist | From 3.6.0-rc1 | 3.6.3 |

## How do I fix GHSA-4qx8-j9vh-2628?

Upgrade silverstripe/framework to a fixed version for your release line: 3.5.6 or 3.6.3.

## Is GHSA-4qx8-j9vh-2628 being exploited?

There is no known exploitation of GHSA-4qx8-j9vh-2628 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4qx8-j9vh-2628 and fix it if it is affected.

What it is: GHSA-4qx8-j9vh-2628 is a vulnerability in silverstripe/framework, published on 27 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-4qx8-j9vh-2628 in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/framework (Packagist): affected from 3.5.0-rc1; fixed in 3.5.6
- silverstripe/framework (Packagist): affected from 3.5.0-rc1; fixed in 3.5.6
- silverstripe/framework (Packagist): affected from 3.6.0-rc1; fixed in 3.6.3
- silverstripe/framework (Packagist): affected from 3.6.0-rc1; fixed in 3.6.3

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-4qx8-j9vh-2628/ (Markdown: https://insights.sbomify.com/GHSA-4qx8-j9vh-2628/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4qx8-j9vh-2628

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4qx8-j9vh-2628/
Summaries are generated and may contain mistakes; the official description above is the record.