GHSA-9cw3-j7wg-jwj8: Neos/flow Neos Flow Information Disclosure Vulnerability

MODERATE
CVSS 4.3
Published
Advisory Summary

GHSA-9cw3-j7wg-jwj8 is a MODERATE (CVSS 4.3) neos flow information disclosure vulnerability (General Security Weakness) affecting Neos/flow libraries in the Packagist ecosystem. The issue involves neos flow information disclosure in entity security. Remediation is available by upgrading affected packages to version 3.0.12, 3.1.10, 3.2.13, 3.3.13, 4.0.6.

GHSA-9cw3-j7wg-jwj8 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-9cw3-j7wg-jwj8
Severity MODERATE
CVSS v3.1 Base Score 4.3
CWE Classification General Security Weakness
Affected Product Neos/flow
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 4.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix GHSA-9cw3-j7wg-jwj8

To remediate this vulnerability, upgrade all affected Neos/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.

neos/flow fixed: 3.0.12
Upgrade neos/flow to 3.0.12
neos/flow fixed: 3.1.10
Upgrade neos/flow to 3.1.10
neos/flow fixed: 3.2.13
Upgrade neos/flow to 3.2.13
neos/flow fixed: 3.3.13
Upgrade neos/flow to 3.3.13
neos/flow fixed: 4.0.6
Upgrade neos/flow to 4.0.6
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 neos/flow

How to Check if You Are Affected

To determine whether your application is affected by GHSA-9cw3-j7wg-jwj8, inspect your project dependencies for Neos/flow:

inspect dependencies for neos/flow

Analyze the terminal output to locate any version of Neos/flow in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.0.12), 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 Neos/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

If you had used entity security and wanted to secure entities not just based on the user's role, but on some property of the user (like the company he belongs to), entity security did not work properly together with the doctrine query cache. This could lead to other users re-using SQL queries from the cache which were built for other users; and thus users could see entities which were not destined for them. ### Am I affected? - Do you use Entity Security? if no, you are not affected. - You disabled the Doctrine Cache (Flow_Persistence_Doctrine)? If this is the case, you are not affected. - You use Entity Security in custom Flow or Neos applications. Read on. - If you only used Entity Security based on roles (i.e. role A was allowed to see entities, but role B was denied): In this case, you are not affected. - If you did more advanced stuff using Entity Security (like checking that a customer only sees his own orders; or a hotel only sees its own bookings), you very likely needed to register a custom global object in Neos.Flow.aop.globalObjects. In this case, you are affected by the issue; and need to implement the CacheAwareInterface in your global object for proper caching. All Flow versions (starting in version 3.0, where Entity Security was introduced) were affected.

GHSA-9cw3-j7wg-jwj8 Affected Neos/flow Versions

5 component(s)
Fixed Versions:
3.0.123.1.103.2.133.3.134.0.6
Product / Package Ecosystem Affected Versions Fixed Version
neos/flow
Packagist
≥ 3.0.0
< 3.0.12
3.0.12
neos/flow
Packagist
≥ 3.1.0
< 3.1.10
3.1.10
neos/flow
Packagist
≥ 3.2.0
< 3.2.13
3.2.13
neos/flow
Packagist
≥ 3.3.0
< 3.3.13
3.3.13
neos/flow
Packagist
≥ 4.0.0
< 4.0.6
4.0.6

References

Frequently Asked Questions

What is GHSA-9cw3-j7wg-jwj8?
GHSA-9cw3-j7wg-jwj8 is a security vulnerability in Neos/flow involving Neos Flow Information disclosure in entity security under General Security Weakness.
Which Neos/flow versions are affected?
Affected versions include releases prior to 3.0.12, 3.1.10, 3.2.13, 3.3.13, 4.0.6 across affected packages: neos/flow.
What version fixes GHSA-9cw3-j7wg-jwj8?
Upgrading to 3.0.12, 3.1.10, 3.2.13, 3.3.13, 4.0.6 (or the latest patched release for your respective branch) resolves the vulnerability.
Is neos/flow affected?
Yes, neos/flow is affected in releases prior to 3.0.12, 3.1.10, 3.2.13, 3.3.13, 4.0.6. Upgrade your dependency to 3.0.12, 3.1.10, 3.2.13, 3.3.13, 4.0.6 or later.
What is the CVSS score of GHSA-9cw3-j7wg-jwj8?
GHSA-9cw3-j7wg-jwj8 has a CVSS v3.1 base score of 4.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with GHSA-9cw3-j7wg-jwj8?
GHSA-9cw3-j7wg-jwj8 is classified under General Security Weakness.
How can I check Packagist dependencies for GHSA-9cw3-j7wg-jwj8?
Run the dependency tree command: 'inspect dependencies for neos/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-9cw3-j7wg-jwj8",
  "modified" : "2024-05-17T22:54:45Z",
  "published" : "2024-05-17T22:54:45Z",
  "aliases" : [ ],
  "summary" : "Neos Flow Information disclosure in entity security",
  "details" : "If you had used entity security and wanted to secure entities not just based on the user's role, but on some property of the user (like the company he belongs to), entity security did not work properly together with the doctrine query cache. This could lead to other users re-using SQL queries from the cache which were built for other users; and thus users could see entities which were not destined for them.\n\n### Am I affected?\n\n- Do you use Entity Security? if no, you are not affected.\n- You disabled the Doctrine Cache (Flow_Persistence_Doctrine)? If this is the case, you are not affected.\n- You use Entity Security in custom Flow or Neos applications. Read on.\n  - If you only used Entity Security based on roles (i.e. role A was allowed to see entities, but role B was denied): In this case, you are not affected.\n  - If you did more advanced stuff using Entity Security (like checking that a customer only sees his own orders; or a hotel only sees its own bookings), you very likely needed to register a custom global object in Neos.Flow.aop.globalObjects. In this case, you are affected by the issue; and need to implement the CacheAwareInterface in your global object for proper caching.\n\nAll Flow versions (starting in version 3.0, where Entity Security was introduced) were affected.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "neos/flow"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0"
      }, {
        "fixed" : "3.0.12"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "neos/flow"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.1.0"
      }, {
        "fixed" : "3.1.10"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "neos/flow"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.2.0"
      }, {
        "fixed" : "3.2.13"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "neos/flow"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.3.0"
      }, {
        "fixed" : "3.3.13"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "neos/flow"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0"
      }, {
        "fixed" : "4.0.6"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/neos/flow/2017-04-12.yaml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/neos/flow"
  }, {
    "type" : "WEB",
    "url" : "https://www.neos.io/blog/flow-bugfix-releases-for-entity-security.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-05-17T22:54:45Z",
    "nvd_published_at" : null
  }
}