{"answers":{"affected":"4 open source packages ship an affected version, including silverstripe/framework.","exploited":"There is no known exploitation of GHSA-crr3-h4m8-7f56 in the wild and no public exploit code.","fix":"Upgrade silverstripe/framework to a fixed version for your release line: 4.0.4 or 4.1.1.","what":"GHSA-crr3-h4m8-7f56 is a vulnerability in silverstripe/framework, published on 27 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-crr3-h4m8-7f56 and fix it if it is affected.\n\nWhat it is: GHSA-crr3-h4m8-7f56 is a vulnerability in silverstripe/framework, published on 27 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-crr3-h4m8-7f56 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/framework (Packagist): affected from 4.0.0-rc1; fixed in 4.0.4\n- silverstripe/framework (Packagist): affected from 4.0.0-rc1; fixed in 4.0.4\n- silverstripe/framework (Packagist): affected from 4.1.0-rc1; fixed in 4.1.1\n- silverstripe/framework (Packagist): affected from 4.1.0-rc1; fixed in 4.1.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-crr3-h4m8-7f56/ (Markdown: https://insights.sbomify.com/GHSA-crr3-h4m8-7f56/index.md)","id":"GHSA-crr3-h4m8-7f56","markdown":"https://insights.sbomify.com/GHSA-crr3-h4m8-7f56/index.md","name":"GHSA-crr3-h4m8-7f56","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SilverStripe framework","requires_auth":"none","summary":"An attacker can enumerate valid user accounts by observing differences in login lockout messages for existing versus non-existent users.","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":"There is a user ID enumeration vulnerability in our brute force error messages.\n\n- Users that don't exist in will never get a locked out message\n- Users that do exist, will get a locked out message\n\nThis means an attacker can infer or confirm user details that exist in the member table.\n\nThis issue has been resolved by ensuring that login attempt logging and lockout process works equivalently for non-existent users as it does for existant users.\n\nThis is a regression of [SS-2017-002](https://www.silverstripe.org/download/security-releases/ss-2017-002).","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":"silverstripe/framework vulnerable to member disclosure in login form","id":"GHSA-crr3-h4m8-7f56","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":4,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["4.0.4"],"introduced":["4.0.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-crr3-h4m8-7f56"},{"ecosystem":"Packagist","fixed":["4.0.4"],"introduced":["4.0.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-crr3-h4m8-7f56"},{"ecosystem":"Packagist","fixed":["4.1.1"],"introduced":["4.1.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-crr3-h4m8-7f56"},{"ecosystem":"Packagist","fixed":["4.1.1"],"introduced":["4.1.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-crr3-h4m8-7f56"}],"products":null,"published":"2024-05-27","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 enumerate valid user accounts by observing differences in login lockout messages for existing versus non-existent users.","url":"https://insights.sbomify.com/GHSA-crr3-h4m8-7f56/"}