# GHSA-g4xv-r3qw-v3q2: typo3 Information Disclosure Security Note > Unauthenticated attackers can read internal Neos CMS workspaces if they guess the workspace name and hash, exposing non-public content. - **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-g4xv-r3qw-v3q2? GHSA-g4xv-r3qw-v3q2 is a vulnerability in typo3/neos, 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 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. ## Which versions are affected by GHSA-g4xv-r3qw-v3q2? 18 open source packages ship an affected version, including typo3/neos. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `typo3/neos` | Packagist | From 2.3.0 | 2.3.99 | | `typo3/neos` | Packagist | From 2.3.0 | 2.3.99 | | `typo3/neos` | Packagist | From 3.0.0 | 3.0.20 | | `typo3/neos` | Packagist | From 3.0.0 | 3.0.20 | | `typo3/neos` | Packagist | From 3.1.0 | 3.1.18 | | `typo3/neos` | Packagist | From 3.1.0 | 3.1.18 | | `typo3/neos` | Packagist | From 3.2.0 | 3.2.14 | | `typo3/neos` | Packagist | From 3.2.0 | 3.2.14 | | `typo3/neos` | Packagist | From 3.3.0 | 3.3.23 | | `typo3/neos` | Packagist | From 3.3.0 | 3.3.23 | | `typo3/neos` | Packagist | From 4.0.0 | 4.0.17 | | `typo3/neos` | Packagist | From 4.0.0 | 4.0.17 | | `typo3/neos` | Packagist | From 4.1.0 | 4.1.16 | | `typo3/neos` | Packagist | From 4.1.0 | 4.1.16 | | `typo3/neos` | Packagist | From 4.2.0 | 4.2.12 | | `typo3/neos` | Packagist | From 4.2.0 | 4.2.12 | | `typo3/neos` | Packagist | From 4.3.0 | 4.3.3 | | `typo3/neos` | Packagist | From 4.3.0 | 4.3.3 | ## How do I fix GHSA-g4xv-r3qw-v3q2? Upgrade typo3/neos to a fixed version for your release line: 2.3.99, 3.0.20, 3.1.18 or 3.2.14. ## Is GHSA-g4xv-r3qw-v3q2 being exploited? There is no known exploitation of GHSA-g4xv-r3qw-v3q2 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-g4xv-r3qw-v3q2 and fix it if it is affected. What it is: GHSA-g4xv-r3qw-v3q2 is a vulnerability in typo3/neos, 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-g4xv-r3qw-v3q2 in the wild and no public exploit code. Affected packages and fixed versions: - typo3/neos (Packagist): affected from 2.3.0; fixed in 2.3.99 - typo3/neos (Packagist): affected from 2.3.0; fixed in 2.3.99 - typo3/neos (Packagist): affected from 3.0.0; fixed in 3.0.20 - typo3/neos (Packagist): affected from 3.0.0; fixed in 3.0.20 - typo3/neos (Packagist): affected from 3.1.0; fixed in 3.1.18 - typo3/neos (Packagist): affected from 3.1.0; fixed in 3.1.18 - typo3/neos (Packagist): affected from 3.2.0; fixed in 3.2.14 - typo3/neos (Packagist): affected from 3.2.0; fixed in 3.2.14 - typo3/neos (Packagist): affected from 3.3.0; fixed in 3.3.23 - typo3/neos (Packagist): affected from 3.3.0; fixed in 3.3.23 - typo3/neos (Packagist): affected from 4.0.0; fixed in 4.0.17 - typo3/neos (Packagist): affected from 4.0.0; fixed in 4.0.17 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-g4xv-r3qw-v3q2/ (Markdown: https://insights.sbomify.com/GHSA-g4xv-r3qw-v3q2/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-g4xv-r3qw-v3q2 --- From sbomify Insights: https://insights.sbomify.com/GHSA-g4xv-r3qw-v3q2/ Summaries are generated and may contain mistakes; the official description above is the record.