{"answers":{"affected":"2 open source packages ship an affected version, including symfony/symfony.","exploited":"There is no known exploitation of GHSA-7mx2-7q8p-pgmw in the wild and no public exploit code.","fix":"Upgrade symfony/symfony to 2.0.6 or later.","what":"GHSA-7mx2-7q8p-pgmw is an authentication bypass vulnerability in symfony/symfony, published on 30 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for GHSA-7mx2-7q8p-pgmw and fix it if it is affected.\n\nWhat it is: GHSA-7mx2-7q8p-pgmw is an authentication bypass vulnerability in symfony/symfony, published on 30 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of GHSA-7mx2-7q8p-pgmw in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- symfony/symfony (Packagist): affected from 2.0.0; fixed in 2.0.6\n- symfony/symfony (Packagist): affected from 2.0.0; fixed in 2.0.6\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-7mx2-7q8p-pgmw/ (Markdown: https://insights.sbomify.com/GHSA-7mx2-7q8p-pgmw/index.md)","id":"GHSA-7mx2-7q8p-pgmw","markdown":"https://insights.sbomify.com/GHSA-7mx2-7q8p-pgmw/index.md","name":"GHSA-7mx2-7q8p-pgmw","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"Symfony PHP framework","requires_auth":"low_privilege","summary":"Authenticated users can switch identities to other users by modifying their username in a form, leading to account takeover.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Symfony 2.0.6 has just been released. It addresses a security vulnerability in the EntityUserProvider as provided in the Doctrine bridge.\n\nIf you let your users update their login/username from a form, and if you are using Doctrine as a user provider, then you are vulnerable and you should upgrade as soon as possible.\n\nThe issue is that it is possible for a user to switch to another one. Here is how to reproduce it: The current user changes its username via a form to another existing username. When the form is submitted, he will have a validation error (as the username already exists) but the user object in the session will still be modified to the new username. This user from the session will be used for the next requests and so the user will be switched to this other user.\n\nThe fix is to always refresh the user via the primary key (which cannot be updated via a form) instead of the username.\n\nIf you cannot upgrade immediately, please apply the following patch: https://github.com/symfony/symfony/commit/9d2ab9ca9c1762","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":"Symfony may allow a user to switch to using another user's identity","id":"GHSA-7mx2-7q8p-pgmw","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["2.0.6"],"introduced":["2.0.0"],"last_affected":[],"package":"symfony/symfony","purl":null,"source":"GHSA-7mx2-7q8p-pgmw"},{"ecosystem":"Packagist","fixed":["2.0.6"],"introduced":["2.0.0"],"last_affected":[],"package":"symfony/symfony","purl":"pkg:composer/symfony/symfony","source":"GHSA-7mx2-7q8p-pgmw"}],"products":null,"published":"2024-05-30","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":"Authenticated users can switch identities to other users by modifying their username in a form, leading to account takeover.","url":"https://insights.sbomify.com/GHSA-7mx2-7q8p-pgmw/"}