{"answers":{"affected":"2 open source packages ship an affected version, including neos/flow.","exploited":"There is no known exploitation of GHSA-7h74-7vcw-4mwp in the wild and no public exploit code.","fix":"Upgrade neos/flow to 1.0.4 or later.","what":"GHSA-7h74-7vcw-4mwp is an unsafe deserialization vulnerability in neos/flow, 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-7h74-7vcw-4mwp and fix it if it is affected.\n\nWhat it is: GHSA-7h74-7vcw-4mwp is an unsafe deserialization vulnerability in neos/flow, 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-7h74-7vcw-4mwp in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- neos/flow (Packagist): affected from 1.0.0; fixed in 1.0.4\n- neos/flow (Packagist): affected from 1.0.0; fixed in 1.0.4\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-7h74-7vcw-4mwp/ (Markdown: https://insights.sbomify.com/GHSA-7h74-7vcw-4mwp/index.md)","id":"GHSA-7h74-7vcw-4mwp","markdown":"https://insights.sbomify.com/GHSA-7h74-7vcw-4mwp/index.md","name":"GHSA-7h74-7vcw-4mwp","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"FLOW3 framework","requires_auth":"none","summary":"An attacker can trigger arbitrary object deserialization in FLOW3 due to missing HMAC signatures, potentially leading to code execution if exploitable objects exist.","user_interaction":"not_required","vuln_class":"deserialization"},"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 a missing signature (HMAC) for a request argument, an attacker could unserialize arbitrary objects within FLOW3.\n\nTo our knowledge it is neither possible to inject code through this vulnerability, nor are there exploitable objects within the FLOW3 Base Distribution. However, there might be exploitable objects within user applications.","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":"Insecure deserialize Vulnerability in FLOW3","id":"GHSA-7h74-7vcw-4mwp","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"deserialization","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["1.0.4"],"introduced":["1.0.0"],"last_affected":[],"package":"neos/flow","purl":null,"source":"GHSA-7h74-7vcw-4mwp"},{"ecosystem":"Packagist","fixed":["1.0.4"],"introduced":["1.0.0"],"last_affected":[],"package":"neos/flow","purl":"pkg:composer/neos/flow","source":"GHSA-7h74-7vcw-4mwp"}],"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":"An attacker can trigger arbitrary object deserialization in FLOW3 due to missing HMAC signatures, potentially leading to code execution if exploitable objects exist.","url":"https://insights.sbomify.com/GHSA-7h74-7vcw-4mwp/"}