# GHSA-m2hp-5x78-74mg: Insecure Unserialize Vulnerability in FLOW3

> An attacker can unserialize arbitrary objects in FLOW3 due to missing HMAC signatures, potentially leading to code execution in user applications.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jun 2024

## What is GHSA-m2hp-5x78-74mg?

GHSA-m2hp-5x78-74mg is an unsafe deserialization vulnerability in typo3/flow, published on 5 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Due to a missing signature (HMAC) for a request argument, an attacker could unserialize arbitrary objects within FLOW3.

To our knowledge it is neither possible to inject code through this vulnerability, nor are there exploitable objects within the FLOW3 Base Distribution. However, there might be exploitable objects within user applications.

## Which versions are affected by GHSA-m2hp-5x78-74mg?

2 open source packages ship an affected version, including typo3/flow.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/flow` | Packagist | From 1.0.0 | 1.0.4 |
| `typo3/flow` | Packagist | From 1.0.0 | 1.0.4 |

## How do I fix GHSA-m2hp-5x78-74mg?

Upgrade typo3/flow to 1.0.4 or later.

## Is GHSA-m2hp-5x78-74mg being exploited?

There is no known exploitation of GHSA-m2hp-5x78-74mg in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-m2hp-5x78-74mg and fix it if it is affected.

What it is: GHSA-m2hp-5x78-74mg is an unsafe deserialization vulnerability in typo3/flow, published on 5 Jun 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-m2hp-5x78-74mg in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/flow (Packagist): affected from 1.0.0; fixed in 1.0.4
- typo3/flow (Packagist): affected from 1.0.0; fixed in 1.0.4

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-m2hp-5x78-74mg/ (Markdown: https://insights.sbomify.com/GHSA-m2hp-5x78-74mg/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-m2hp-5x78-74mg

---
From sbomify Insights: https://insights.sbomify.com/GHSA-m2hp-5x78-74mg/
Summaries are generated and may contain mistakes; the official description above is the record.