Neos Information Disclosure Security Note
Published 17 May 2024 · Updated 2 Dec 2024
Is your project on an affected neos/neos?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=2.3.0 <3.0.20
- Fixed in
- 3.0.20
composer require neos/neos:^3.0.20- Affected
- >=3.1.0 <3.1.18
- Fixed in
- 3.1.18
composer require neos/neos:^3.1.18- Affected
- >=3.2.0 <3.2.14
- Fixed in
- 3.2.14
composer require neos/neos:^3.2.14- Affected
- >=3.3.0 <3.3.23
- Fixed in
- 3.3.23
composer require neos/neos:^3.3.23- Affected
- >=4.0.0 <4.0.17
- Fixed in
- 4.0.17
composer require neos/neos:^4.0.17- Affected
- >=4.1.0 <4.1.16
- Fixed in
- 4.1.16
composer require neos/neos:^4.1.16- Affected
- >=4.2.0 <4.2.12
- Fixed in
- 4.2.12
composer require neos/neos:^4.2.12- Affected
- >=4.3.0 <4.3.3
- Fixed in
- 4.3.3
composer require neos/neos:^4.3.3Details
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.
Is GHSA-3c5g-73f7-grvm in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected neos/neos, and gives you the command that fixes it.
More advisories for neos/neos
- HighGHSA-6cj3-rc4p-f38fCross-site Scripting vulnerabilities in Neos · 17 May 2024
- MediumGHSA-43cf-7f3h-38rgPrivilege Escalation in TYPO3 Neos · 17 May 2024
- MediumCVE-2022-30429Neos CMS vulnerable to XSS in various backend modules · 3 Jun 2022
- MediumGHSA-jfxf-4frr-9j3qXSS in various backend modules due to (un)escaping in JS notification module · 25 May 2022
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.