GHSA-g4xv-r3qw-v3q2: typo3 Information Disclosure Security Note
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.
Published Jun 5, 2024
Affected packages
typo3/neos
- Ecosystem
- Composer (PHP)
- Affected
- >= 2.3.0, < 2.3.99
- Fixed in
- 2.3.99
- Check
composer show typo3/neos
typo3/neos
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.0.0, < 3.0.20
- Fixed in
- 3.0.20
- Check
composer show typo3/neos
typo3/neos
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.1.0, < 3.1.18
- Fixed in
- 3.1.18
- Check
composer show typo3/neos
typo3/neos
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.2.0, < 3.2.14
- Fixed in
- 3.2.14
- Check
composer show typo3/neos
typo3/neos
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.3.0, < 3.3.23
- Fixed in
- 3.3.23
- Check
composer show typo3/neos
typo3/neos
- Ecosystem
- Composer (PHP)
- Affected
- >= 4.0.0, < 4.0.17
- Fixed in
- 4.0.17
- Check
composer show typo3/neos
typo3/neos
- Ecosystem
- Composer (PHP)
- Affected
- >= 4.1.0, < 4.1.16
- Fixed in
- 4.1.16
- Check
composer show typo3/neos
typo3/neos
- Ecosystem
- Composer (PHP)
- Affected
- >= 4.2.0, < 4.2.12
- Fixed in
- 4.2.12
- Check
composer show typo3/neos
typo3/neos
- Ecosystem
- Composer (PHP)
- Affected
- >= 4.3.0, < 4.3.3
- Fixed in
- 4.3.3
- Check
composer show typo3/neos
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
