# GHSA-6wqp-7g94-f69j: sensiolabs/connect has a Cross-Site Request Forgery Vulnerability

> Attackers can exploit missing OAuth state parameters to perform CSRF attacks, potentially taking over user accounts.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 May 2024

## What is GHSA-6wqp-7g94-f69j?

GHSA-6wqp-7g94-f69j is a vulnerability in sensiolabs/connect, published on 21 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Versions of sensiolabs/connect prior to 4.2.3 are affected by a Cross-Site Request Forgery (CSRF) vulnerability due to the absence of the state parameter in OAuth requests. The lack of proper state parameter handling exposes applications to CSRF attacks during the OAuth authentication flow.

## Which versions are affected by GHSA-6wqp-7g94-f69j?

2 open source packages ship an affected version, including sensiolabs/connect.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sensiolabs/connect` | Packagist | All versions | 4.2.3 |
| `sensiolabs/connect` | Packagist | All versions | 4.2.3 |

## How do I fix GHSA-6wqp-7g94-f69j?

Upgrade sensiolabs/connect to 4.2.3 or later.

## Is GHSA-6wqp-7g94-f69j being exploited?

There is no known exploitation of GHSA-6wqp-7g94-f69j in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-6wqp-7g94-f69j and fix it if it is affected.

What it is: GHSA-6wqp-7g94-f69j is a vulnerability in sensiolabs/connect, published on 21 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-6wqp-7g94-f69j in the wild and no public exploit code.

Affected packages and fixed versions:
- sensiolabs/connect (Packagist): affected all versions; fixed in 4.2.3
- sensiolabs/connect (Packagist): affected all versions; fixed in 4.2.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-6wqp-7g94-f69j/ (Markdown: https://insights.sbomify.com/GHSA-6wqp-7g94-f69j/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-6wqp-7g94-f69j

---
From sbomify Insights: https://insights.sbomify.com/GHSA-6wqp-7g94-f69j/
Summaries are generated and may contain mistakes; the official description above is the record.