How severe is GHSA-m2hp-5x78-74mg?

No CVSS score has been assigned to GHSA-m2hp-5x78-74mg yet. Review the advisory details and affected package list to assess your exposure.

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

GHSA-m2hp-5x78-74mg affects the following packages: typo3/flow (Packagist). Ecosystems affected: Packagist.

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

Update typo3/flow to 1.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m2hp-5x78-74mg is resolved across your whole dependency graph.

How do I detect GHSA-m2hp-5x78-74mg in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/flow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-m2hp-5x78-74mg if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-m2hp-5x78-74mg actively exploited in the wild?

No public exploit code has been indexed for GHSA-m2hp-5x78-74mg yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-m2hp-5x78-74mg published, and has it been updated?

GHSA-m2hp-5x78-74mg was published on June 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

Insecure Unserialize Vulnerability in FLOW3GHSA-m2hp-5x78-74mg

GHSA-m2hp-5x78-74mg is a security vulnerability in typo3/flow. A fix is available for typo3/flow — see the affected versions and patch details below.

Published

Jun 5, 2024

Updated

Jun 5, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 5, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘typo3/flow

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/flow`	≥ 1.0.0&&< 1.0.4	1.0.4`composer require typo3/flow:^1.0.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/flow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/flow to 1.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m2hp-5x78-74mg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-m2hp-5x78-74mg in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works