{"answers":{"affected":"16 open source packages ship an affected version, including neos/neos.","exploited":"There is no known exploitation of GHSA-3c5g-73f7-grvm in the wild and no public exploit code.","fix":"Upgrade neos/neos to a fixed version for your release line: 3.0.20, 3.1.18, 3.2.14 or 3.3.23.","what":"GHSA-3c5g-73f7-grvm is a vulnerability in neos/neos, published on 17 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-3c5g-73f7-grvm and fix it if it is affected.\n\nWhat it is: GHSA-3c5g-73f7-grvm is a vulnerability in neos/neos, published on 17 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-3c5g-73f7-grvm in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- neos/neos (Packagist): affected from 2.3.0; fixed in 3.0.20\n- neos/neos (Packagist): affected from 2.3.0; fixed in 3.0.20\n- neos/neos (Packagist): affected from 3.1.0; fixed in 3.1.18\n- neos/neos (Packagist): affected from 3.1.0; fixed in 3.1.18\n- neos/neos (Packagist): affected from 3.2.0; fixed in 3.2.14\n- neos/neos (Packagist): affected from 3.2.0; fixed in 3.2.14\n- neos/neos (Packagist): affected from 3.3.0; fixed in 3.3.23\n- neos/neos (Packagist): affected from 3.3.0; fixed in 3.3.23\n- neos/neos (Packagist): affected from 4.0.0; fixed in 4.0.17\n- neos/neos (Packagist): affected from 4.0.0; fixed in 4.0.17\n- neos/neos (Packagist): affected from 4.1.0; fixed in 4.1.16\n- neos/neos (Packagist): affected from 4.1.0; fixed in 4.1.16\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-3c5g-73f7-grvm/ (Markdown: https://insights.sbomify.com/GHSA-3c5g-73f7-grvm/index.md)","id":"GHSA-3c5g-73f7-grvm","markdown":"https://insights.sbomify.com/GHSA-3c5g-73f7-grvm/index.md","name":"GHSA-3c5g-73f7-grvm","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Neos CMS","requires_auth":"none","summary":"Unauthenticated attackers can read internal Neos CMS workspaces if they guess the workspace name and hash, exposing non-public content.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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.\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.","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Neos Information Disclosure Security Note","id":"GHSA-3c5g-73f7-grvm","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":16,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["3.0.20"],"introduced":["2.3.0"],"last_affected":[],"package":"neos/neos","purl":null,"source":"GHSA-3c5g-73f7-grvm"},{"ecosystem":"Packagist","fixed":["3.0.20"],"introduced":["2.3.0"],"last_affected":[],"package":"neos/neos","purl":"pkg:composer/neos/neos","source":"GHSA-3c5g-73f7-grvm"},{"ecosystem":"Packagist","fixed":["3.1.18"],"introduced":["3.1.0"],"last_affected":[],"package":"neos/neos","purl":null,"source":"GHSA-3c5g-73f7-grvm"},{"ecosystem":"Packagist","fixed":["3.1.18"],"introduced":["3.1.0"],"last_affected":[],"package":"neos/neos","purl":"pkg:composer/neos/neos","source":"GHSA-3c5g-73f7-grvm"},{"ecosystem":"Packagist","fixed":["3.2.14"],"introduced":["3.2.0"],"last_affected":[],"package":"neos/neos","purl":null,"source":"GHSA-3c5g-73f7-grvm"},{"ecosystem":"Packagist","fixed":["3.2.14"],"introduced":["3.2.0"],"last_affected":[],"package":"neos/neos","purl":"pkg:composer/neos/neos","source":"GHSA-3c5g-73f7-grvm"},{"ecosystem":"Packagist","fixed":["3.3.23"],"introduced":["3.3.0"],"last_affected":[],"package":"neos/neos","purl":null,"source":"GHSA-3c5g-73f7-grvm"},{"ecosystem":"Packagist","fixed":["3.3.23"],"introduced":["3.3.0"],"last_affected":[],"package":"neos/neos","purl":"pkg:composer/neos/neos","source":"GHSA-3c5g-73f7-grvm"},{"ecosystem":"Packagist","fixed":["4.0.17"],"introduced":["4.0.0"],"last_affected":[],"package":"neos/neos","purl":null,"source":"GHSA-3c5g-73f7-grvm"},{"ecosystem":"Packagist","fixed":["4.0.17"],"introduced":["4.0.0"],"last_affected":[],"package":"neos/neos","purl":"pkg:composer/neos/neos","source":"GHSA-3c5g-73f7-grvm"},{"ecosystem":"Packagist","fixed":["4.1.16"],"introduced":["4.1.0"],"last_affected":[],"package":"neos/neos","purl":null,"source":"GHSA-3c5g-73f7-grvm"},{"ecosystem":"Packagist","fixed":["4.1.16"],"introduced":["4.1.0"],"last_affected":[],"package":"neos/neos","purl":"pkg:composer/neos/neos","source":"GHSA-3c5g-73f7-grvm"},{"ecosystem":"Packagist","fixed":["4.2.12"],"introduced":["4.2.0"],"last_affected":[],"package":"neos/neos","purl":null,"source":"GHSA-3c5g-73f7-grvm"},{"ecosystem":"Packagist","fixed":["4.2.12"],"introduced":["4.2.0"],"last_affected":[],"package":"neos/neos","purl":"pkg:composer/neos/neos","source":"GHSA-3c5g-73f7-grvm"},{"ecosystem":"Packagist","fixed":["4.3.3"],"introduced":["4.3.0"],"last_affected":[],"package":"neos/neos","purl":null,"source":"GHSA-3c5g-73f7-grvm"},{"ecosystem":"Packagist","fixed":["4.3.3"],"introduced":["4.3.0"],"last_affected":[],"package":"neos/neos","purl":"pkg:composer/neos/neos","source":"GHSA-3c5g-73f7-grvm"}],"products":null,"published":"2024-05-17","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Unauthenticated attackers can read internal Neos CMS workspaces if they guess the workspace name and hash, exposing non-public content.","url":"https://insights.sbomify.com/GHSA-3c5g-73f7-grvm/"}