GHSA-g4xv-r3qw-v3q2: Typo3/neos Typo3 Information Disclosure Security Note Vulnerability

HIGH
Published
Advisory Summary

GHSA-g4xv-r3qw-v3q2 is a HIGH typo3 information disclosure security note vulnerability (General Security Weakness) affecting Typo3/neos libraries in the Packagist ecosystem. The issue involves typo3 information disclosure security note. Remediation is available by upgrading affected packages to version 2.3.99, 3.0.20, 3.1.18, 3.2.14, 3.3.23, 4.0.17, 4.1.16, 4.2.12, 4.3.3.

GHSA-g4xv-r3qw-v3q2 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-g4xv-r3qw-v3q2
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Typo3/neos
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix GHSA-g4xv-r3qw-v3q2

To remediate this vulnerability, upgrade all affected Typo3/neos 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/neos fixed: 2.3.99
Upgrade typo3/neos to 2.3.99
typo3/neos fixed: 3.0.20
Upgrade typo3/neos to 3.0.20
typo3/neos fixed: 3.1.18
Upgrade typo3/neos to 3.1.18
typo3/neos fixed: 3.2.14
Upgrade typo3/neos to 3.2.14
typo3/neos fixed: 3.3.23
Upgrade typo3/neos to 3.3.23
typo3/neos fixed: 4.0.17
Upgrade typo3/neos to 4.0.17
typo3/neos fixed: 4.1.16
Upgrade typo3/neos to 4.1.16
typo3/neos fixed: 4.2.12
Upgrade typo3/neos to 4.2.12
typo3/neos fixed: 4.3.3
Upgrade typo3/neos to 4.3.3
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/neos

How to Check if You Are Affected

To determine whether your application is affected by GHSA-g4xv-r3qw-v3q2, inspect your project dependencies for Typo3/neos:

inspect dependencies for typo3/neos

Analyze the terminal output to locate any version of Typo3/neos in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.3.99), 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/neos, 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 reports it has been validated that internal workspaces in Neos are accessible without authentication. Some users assumed this is a planned feature but it is not. A workspace preview should be an additional feature with respective security measures in place. Note that this only allows reading of internal workspaces not writing. And for clarification, an internal workspace is a workspace that is non public and doesn't have an owner. Given that an internal workspace exists in your installation, it is possible to view a page in context of that workspace by opening a link in this format: https://domain/path/to/page.html@workspace-name The issue is quite problematic when exploited but at the same time slightly less impactful than it sounds. First of all there is no default internal workspace, so the issue affects only workspaces created by users. That also means the workspace-name, which will also always include a hash is individual to a project and an exploiter must get hold of the workspace-name including the hash. This is non trivial as there is no indication of the existence of it, but obviously brute force and educated guessed can be made.

GHSA-g4xv-r3qw-v3q2 Affected Typo3/neos Versions

9 component(s)
Fixed Versions:
2.3.993.0.203.1.183.2.143.3.234.0.174.1.164.2.124.3.3
Product / Package Ecosystem Affected Versions Fixed Version
typo3/neos
Packagist
≥ 2.3.0
< 2.3.99
2.3.99
typo3/neos
Packagist
≥ 3.0.0
< 3.0.20
3.0.20
typo3/neos
Packagist
≥ 3.1.0
< 3.1.18
3.1.18
typo3/neos
Packagist
≥ 3.2.0
< 3.2.14
3.2.14
typo3/neos
Packagist
≥ 3.3.0
< 3.3.23
3.3.23
typo3/neos
Packagist
≥ 4.0.0
< 4.0.17
4.0.17
typo3/neos
Packagist
≥ 4.1.0
< 4.1.16
4.1.16
typo3/neos
Packagist
≥ 4.2.0
< 4.2.12
4.2.12
typo3/neos
Packagist
≥ 4.3.0
< 4.3.3
4.3.3

References

Frequently Asked Questions

What is GHSA-g4xv-r3qw-v3q2?
GHSA-g4xv-r3qw-v3q2 is a security vulnerability in Typo3/neos involving typo3 Information Disclosure Security Note under General Security Weakness.
Which Typo3/neos versions are affected?
Affected versions include releases prior to 2.3.99, 3.0.20, 3.1.18, 3.2.14, 3.3.23, 4.0.17, 4.1.16, 4.2.12, 4.3.3 across affected packages: typo3/neos.
What version fixes GHSA-g4xv-r3qw-v3q2?
Upgrading to 2.3.99, 3.0.20, 3.1.18, 3.2.14, 3.3.23, 4.0.17, 4.1.16, 4.2.12, 4.3.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is typo3/neos affected?
Yes, typo3/neos is affected in releases prior to 2.3.99, 3.0.20, 3.1.18, 3.2.14, 3.3.23, 4.0.17, 4.1.16, 4.2.12, 4.3.3. Upgrade your dependency to 2.3.99, 3.0.20, 3.1.18, 3.2.14, 3.3.23, 4.0.17, 4.1.16, 4.2.12, 4.3.3 or later.
What CWE is associated with GHSA-g4xv-r3qw-v3q2?
GHSA-g4xv-r3qw-v3q2 is classified under General Security Weakness.
How can I check Packagist dependencies for GHSA-g4xv-r3qw-v3q2?
Run the dependency tree command: 'inspect dependencies for typo3/neos'. 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-g4xv-r3qw-v3q2",
  "modified" : "2024-06-05T18:33:01Z",
  "published" : "2024-06-05T18:33:01Z",
  "aliases" : [ ],
  "summary" : "typo3 Information Disclosure Security Note",
  "details" : "Due to reports it has been validated that internal workspaces in Neos are accessible without authentication. Some users assumed this is a planned feature but it is not. A workspace preview should be an additional feature with respective security measures in place.\n\nNote that this only allows reading of internal workspaces not writing. And for clarification, an internal workspace is a workspace that is non public and doesn't have an owner.\n\nGiven that an internal workspace exists in your installation, it is possible to view a page in context of that workspace by opening a link in this format:\n\nhttps://domain/path/to/page.html@workspace-name\n\nThe issue is quite problematic when exploited but at the same time slightly less impactful than it sounds. First of all there is no default internal workspace, so the issue affects only workspaces created by users. That also means the workspace-name, which will also always include a hash is individual to a project and an exploiter must get hold of the workspace-name including the hash. This is non trivial as there is no indication of the existence of it, but obviously brute force and educated guessed can be made.\n\n",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/neos"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.3.0"
      }, {
        "fixed" : "2.3.99"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/neos"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0"
      }, {
        "fixed" : "3.0.20"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/neos"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.1.0"
      }, {
        "fixed" : "3.1.18"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/neos"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.2.0"
      }, {
        "fixed" : "3.2.14"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/neos"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.3.0"
      }, {
        "fixed" : "3.3.23"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/neos"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0"
      }, {
        "fixed" : "4.0.17"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/neos"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.1.0"
      }, {
        "fixed" : "4.1.16"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/neos"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.2.0"
      }, {
        "fixed" : "4.2.12"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/neos"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.3.0"
      }, {
        "fixed" : "4.3.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/neos/2019-06-17.yaml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/mneuhaus/TYPO3.Neos"
  }, {
    "type" : "WEB",
    "url" : "https://www.neos.io/blog/neos-workspace-disclosure-security.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-06-05T18:33:01Z",
    "nvd_published_at" : null
  }
}