{"answers":{"affected":"8 open source packages ship an affected version, including silverstripe/framework.","exploited":"There is no known exploitation of GHSA-m2hh-2m46-x6j5 in the wild and no public exploit code.","fix":"Upgrade silverstripe/framework to a fixed version for your release line: 3.7.1, 4.0.5, 4.1.3 or 4.2.2.","what":"GHSA-m2hh-2m46-x6j5 is a vulnerability in silverstripe/framework, published on 28 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-m2hh-2m46-x6j5 and fix it if it is affected.\n\nWhat it is: GHSA-m2hh-2m46-x6j5 is a vulnerability in silverstripe/framework, published on 28 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-m2hh-2m46-x6j5 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/framework (Packagist): affected from 3.7.0-rc1; fixed in 3.7.1\n- silverstripe/framework (Packagist): affected from 3.7.0-rc1; fixed in 3.7.1\n- silverstripe/framework (Packagist): affected from 4.0.0-rc1; fixed in 4.0.5\n- silverstripe/framework (Packagist): affected from 4.0.0-rc1; fixed in 4.0.5\n- silverstripe/framework (Packagist): affected from 4.1.0-rc1; fixed in 4.1.3\n- silverstripe/framework (Packagist): affected from 4.1.0-rc1; fixed in 4.1.3\n- silverstripe/framework (Packagist): affected from 4.2.0-rc1; fixed in 4.2.2\n- silverstripe/framework (Packagist): affected from 4.2.0-rc1; fixed in 4.2.2\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-m2hh-2m46-x6j5/ (Markdown: https://insights.sbomify.com/GHSA-m2hh-2m46-x6j5/index.md)","id":"GHSA-m2hh-2m46-x6j5","markdown":"https://insights.sbomify.com/GHSA-m2hh-2m46-x6j5/index.md","name":"GHSA-m2hh-2m46-x6j5","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"SilverStripe framework","requires_auth":"none","summary":"Attackers can view database credentials in error messages when SilverStripe runs in dev mode with the mysqli driver.","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":"When running SilverStripe 3.7 or 4.x in dev mode with the mysqli database driver, there is a potential to disclose the connection details.\n\nWe have blacklisted the sensitive parts of the connection information from being included in dev mode stack traces when database errors occur.","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 may disclose database credentials during connection failure","id":"GHSA-m2hh-2m46-x6j5","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":8,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["3.7.1"],"introduced":["3.7.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-m2hh-2m46-x6j5"},{"ecosystem":"Packagist","fixed":["3.7.1"],"introduced":["3.7.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-m2hh-2m46-x6j5"},{"ecosystem":"Packagist","fixed":["4.0.5"],"introduced":["4.0.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-m2hh-2m46-x6j5"},{"ecosystem":"Packagist","fixed":["4.0.5"],"introduced":["4.0.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-m2hh-2m46-x6j5"},{"ecosystem":"Packagist","fixed":["4.1.3"],"introduced":["4.1.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-m2hh-2m46-x6j5"},{"ecosystem":"Packagist","fixed":["4.1.3"],"introduced":["4.1.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-m2hh-2m46-x6j5"},{"ecosystem":"Packagist","fixed":["4.2.2"],"introduced":["4.2.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-m2hh-2m46-x6j5"},{"ecosystem":"Packagist","fixed":["4.2.2"],"introduced":["4.2.0-rc1"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-m2hh-2m46-x6j5"}],"products":null,"published":"2024-05-28","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 view database credentials in error messages when SilverStripe runs in dev mode with the mysqli driver.","url":"https://insights.sbomify.com/GHSA-m2hh-2m46-x6j5/"}