GHSA-m2hp-5x78-74mg: Typo3/flow Insecure Unserialize Vulnerability Vulnerability

MODERATE
Published
Advisory Summary

GHSA-m2hp-5x78-74mg is a MODERATE insecure unserialize vulnerability vulnerability (General Security Weakness) affecting Typo3/flow libraries in the Packagist ecosystem. The issue involves insecure unserialize vulnerability in flow3. Remediation is available by upgrading affected packages to version 1.0.4.

GHSA-m2hp-5x78-74mg at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-m2hp-5x78-74mg
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Typo3/flow
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix GHSA-m2hp-5x78-74mg

To remediate this vulnerability, upgrade all affected Typo3/flow dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

typo3/flow fixed: 1.0.4
Upgrade typo3/flow to 1.0.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for typo3/flow

How to Check if You Are Affected

To determine whether your application is affected by GHSA-m2hp-5x78-74mg, inspect your project dependencies for Typo3/flow:

inspect dependencies for typo3/flow

Analyze the terminal output to locate any version of Typo3/flow in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.0.4), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Typo3/flow, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

GHSA-m2hp-5x78-74mg Affected Typo3/flow Versions

1 component(s)
Fixed Versions:
1.0.4
Product / Package Ecosystem Affected Versions Fixed Version
typo3/flow
Packagist
≥ 1.0.0
< 1.0.4
1.0.4

References

Frequently Asked Questions

What is GHSA-m2hp-5x78-74mg?
GHSA-m2hp-5x78-74mg is a security vulnerability in Typo3/flow involving Insecure Unserialize Vulnerability in FLOW3 under General Security Weakness.
Which Typo3/flow versions are affected?
Affected versions include releases prior to 1.0.4 across affected packages: typo3/flow.
What version fixes GHSA-m2hp-5x78-74mg?
Upgrading to 1.0.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is typo3/flow affected?
Yes, typo3/flow is affected in releases prior to 1.0.4. Upgrade your dependency to 1.0.4 or later.
What CWE is associated with GHSA-m2hp-5x78-74mg?
GHSA-m2hp-5x78-74mg is classified under General Security Weakness.
How can I check Packagist dependencies for GHSA-m2hp-5x78-74mg?
Run the dependency tree command: 'inspect dependencies for typo3/flow'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-m2hp-5x78-74mg",
  "modified" : "2024-06-05T20:47:07Z",
  "published" : "2024-06-05T20:47:07Z",
  "aliases" : [ ],
  "summary" : "Insecure Unserialize Vulnerability in FLOW3",
  "details" : "Due to a missing signature (HMAC) for a request argument, an attacker could unserialize arbitrary objects within FLOW3.\n\nTo 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.",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/flow"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.0.0"
      }, {
        "fixed" : "1.0.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/flow/2012-03-28.yaml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/neos/flow"
  }, {
    "type" : "WEB",
    "url" : "https://www.neos.io/blog/flow-sa-2012-001.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-06-05T20:47:07Z",
    "nvd_published_at" : null
  }
}