Component Type: neos/neos and neos/contentrepository packages
Vulnerability Type: information disclosure
Severity: medium
Affected Versions: Neos from at least version 2.3 upwards
Suggested CVSS: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:P/RL:O/RC:C/CR:L/IR:L/AR:L
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.
Fixing the Issue
To fix the issue, you need to update neos/neos and neos/contentrepository to the newest bugfix versions.
Note: The last supported version for security fixes is Neos 2.3, and that is the only branch for which a tagged version does not exist yet due to dependency issues in our build system. Using 2.3.x-dev should be fine as the bugfix is applied to the branch and nothing else happened. We will tag a version as soon as possible but if you are still using Neos 2.3 we would urge you to update immediately anyway.
Make sure you have at least one of the following versions after updating:
- 3.0.20
- 3.1.18
- 3.2.14
- 3.3.23
- 4.0.17
- 4.1.16
- 4.2.12
- 4.3.3
Getting Help
In case you are unsure about the issue, don't hesitate to contact the Neos team on Slack (#neos-general) or through the other communication channels!