{"answers":{"affected":"4 open source packages ship an affected version, including symfony/security-http and symfony/symfony.","exploited":"There is no known exploitation of GHSA-g2qj-pmxm-9f8f in the wild and no public exploit code.","fix":"Upgrade symfony/security-http to 5.2.8 or later.","what":"GHSA-g2qj-pmxm-9f8f is a vulnerability in symfony/security-http, published on 17 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-g2qj-pmxm-9f8f and fix it if it is affected.\n\nWhat it is: GHSA-g2qj-pmxm-9f8f is a vulnerability in symfony/security-http, published on 17 May 2021. 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-g2qj-pmxm-9f8f in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- symfony/security-http (Packagist): affected from 5.1.0; fixed in 5.2.8\n- symfony/security-http (Packagist): affected from 5.1.0; fixed in 5.2.8\n- symfony/symfony (Packagist): affected from 5.1.0; fixed in 5.2.8\n- symfony/symfony (Packagist): affected from 5.1.0; fixed in 5.2.8\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-g2qj-pmxm-9f8f/ (Markdown: https://insights.sbomify.com/GHSA-g2qj-pmxm-9f8f/index.md)","id":"GHSA-g2qj-pmxm-9f8f","markdown":"https://insights.sbomify.com/GHSA-g2qj-pmxm-9f8f/index.md","name":"GHSA-g2qj-pmxm-9f8f","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Symfony PHP framework","requires_auth":"none","summary":"Attackers can enumerate valid usernames via distinct error messages or timing differences in Symfony authentication, requiring a patch to standardize responses.","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":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available [here](https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011) for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","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":"User enumeration in authentication mechanisms","id":"GHSA-g2qj-pmxm-9f8f","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":4,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["5.2.8"],"introduced":["5.1.0"],"last_affected":[],"package":"symfony/security-http","purl":null,"source":"GHSA-g2qj-pmxm-9f8f"},{"ecosystem":"Packagist","fixed":["5.2.8"],"introduced":["5.1.0"],"last_affected":[],"package":"symfony/security-http","purl":"pkg:composer/symfony/security-http","source":"GHSA-g2qj-pmxm-9f8f"},{"ecosystem":"Packagist","fixed":["5.2.8"],"introduced":["5.1.0"],"last_affected":[],"package":"symfony/symfony","purl":null,"source":"GHSA-g2qj-pmxm-9f8f"},{"ecosystem":"Packagist","fixed":["5.2.8"],"introduced":["5.1.0"],"last_affected":[],"package":"symfony/symfony","purl":"pkg:composer/symfony/symfony","source":"GHSA-g2qj-pmxm-9f8f"}],"products":null,"published":"2021-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":"Attackers can enumerate valid usernames via distinct error messages or timing differences in Symfony authentication, requiring a patch to standardize responses.","url":"https://insights.sbomify.com/GHSA-g2qj-pmxm-9f8f/"}