{"answers":{"affected":"4 open source packages ship an affected version, including neos/flow.","exploited":"There is no known exploitation of GHSA-5vv7-j593-mgjc in the wild and no public exploit code.","fix":"Upgrade neos/flow to a fixed version for your release line: 2.3.7 or 3.0.1.","what":"GHSA-5vv7-j593-mgjc is a vulnerability in neos/flow, published on 17 May 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-5vv7-j593-mgjc and fix it if it is affected.\n\nWhat it is: GHSA-5vv7-j593-mgjc is a vulnerability in neos/flow, published on 17 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-5vv7-j593-mgjc in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- neos/flow (Packagist): affected from 2.3.0; fixed in 2.3.7\n- neos/flow (Packagist): affected from 2.3.0; fixed in 2.3.7\n- neos/flow (Packagist): affected from 3.0.0; fixed in 3.0.1\n- neos/flow (Packagist): affected from 3.0.0; fixed in 3.0.1\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-5vv7-j593-mgjc/ (Markdown: https://insights.sbomify.com/GHSA-5vv7-j593-mgjc/index.md)","id":"GHSA-5vv7-j593-mgjc","markdown":"https://insights.sbomify.com/GHSA-5vv7-j593-mgjc/index.md","name":"GHSA-5vv7-j593-mgjc","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Neos Flow framework","requires_auth":"low_privilege","summary":"Arbitrary file upload in Neos Flow allows remote code execution if the application permits uploads and the server executes uploaded scripts.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"It has been discovered that Flow 3.0.0 allows arbitrary file uploads, inlcuding server-side scripts, posing the risk of attacks. If those scripts are executed by the server when accessed through their public URL, anything not blocked through other means is possible (information disclosure, placement of backdoors, data removal, …).\n\nNote: The upload of files is only possible if the application built on Flow provides means to do so, and whether or not the upload of files poses a risk is dependent on the system setup. If uploaded script files are not executed by the server, there is no risk. In versions prior to 3.0.0 the upload of files with the extension php was blocked.\n\nIn Flow 2.3.0 to 2.3.6 a potential XML External Entity processing vulnerability has been discovered in the MediaTypeConverter.","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 Flow Arbitrary file upload and XML External Entity processing","id":"GHSA-5vv7-j593-mgjc","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"file_upload","year":"2024"},"n_packages":4,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["2.3.7"],"introduced":["2.3.0"],"last_affected":[],"package":"neos/flow","purl":null,"source":"GHSA-5vv7-j593-mgjc"},{"ecosystem":"Packagist","fixed":["2.3.7"],"introduced":["2.3.0"],"last_affected":[],"package":"neos/flow","purl":"pkg:composer/neos/flow","source":"GHSA-5vv7-j593-mgjc"},{"ecosystem":"Packagist","fixed":["3.0.1"],"introduced":["3.0.0"],"last_affected":[],"package":"neos/flow","purl":null,"source":"GHSA-5vv7-j593-mgjc"},{"ecosystem":"Packagist","fixed":["3.0.1"],"introduced":["3.0.0"],"last_affected":[],"package":"neos/flow","purl":"pkg:composer/neos/flow","source":"GHSA-5vv7-j593-mgjc"}],"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":"Arbitrary file upload in Neos Flow allows remote code execution if the application permits uploads and the server executes uploaded scripts.","url":"https://insights.sbomify.com/GHSA-5vv7-j593-mgjc/"}