{"answers":{"affected":"7 open source packages ship an affected version, including silverstripe/framework, silverstripe and silverstripe/cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-6164 in the wild and no public exploit code.","fix":"Upgrade silverstripe/framework to a fixed version for your release line: 4.4.7 or 4.5.4.","what":"CVE-2020-6164 is a high-severity vulnerability in Silverstripe Silverstripe, published on 15 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-6164 and fix it if it is affected.\n\nWhat it is: CVE-2020-6164 is a high-severity vulnerability in Silverstripe Silverstripe, published on 15 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-6164 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/framework (Packagist): affected from 4.0.0; fixed in 4.4.7\n- silverstripe/framework (Packagist): affected from 4.0.0; fixed in 4.4.7\n- silverstripe/framework (Packagist): affected from 4.5.0; fixed in 4.5.4\n- silverstripe/framework (Packagist): affected from 4.5.0; fixed in 4.5.4\n- silverstripe (Bitnami): affected all versions; fixed in 3.0.0, 4.4.7, 4.5.4\n- silverstripe/cms (Packagist): affected all versions up to 4.5.0; no fix listed\n- silverstripe/cms (Packagist): affected all versions up to 4.5.0; no fix listed\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/CVE-2020-6164/ (Markdown: https://insights.sbomify.com/CVE-2020-6164/index.md)","id":"CVE-2020-6164","markdown":"https://insights.sbomify.com/CVE-2020-6164/index.md","name":"CVE-2020-6164","record":{"aliases":["BIT-silverstripe-2020-6164","GHSA-gm5x-hpmw-xpxg"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SilverStripe CMS","requires_auth":"none","summary":"Attackers can identify SilverStripe hosting via a default URL path, revealing the technology stack without exposing version details.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"silverstripe","vendor":"silverstripe"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"In SilverStripe through 4.5.0, a specific URL path configured by default through the silverstripe/framework module can be used to disclose the fact that a domain is hosting a Silverstripe application. There is no disclosure of the specific version. The functionality on this URL path is limited to execution in a CLI context, and is not known to present a vulnerability through web-based access. As a side-effect, this preconfigured path also blocks the creation of other resources on this path (e.g. a page).","ecosystems":["Bitnami","Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Silverstripe CMS information disclosure","id":"CVE-2020-6164","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"silverstripe:silverstripe","products":["silverstripe:silverstripe"],"type":"information_disclosure","year":"2020"},"n_packages":7,"n_references":1,"next":{"headline":"Silverstripe has Incorrect Default Permissions","id":"CVE-2020-6165"},"packages":[{"ecosystem":"Bitnami","fixed":["3.0.0","4.4.7","4.5.4"],"introduced":["0","4.0.0","4.5.0"],"last_affected":[],"package":"silverstripe","purl":"pkg:bitnami/silverstripe","source":"BIT-silverstripe-2020-6164"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["4.5.0"],"package":"silverstripe/cms","purl":null,"source":"GHSA-gm5x-hpmw-xpxg"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["4.5.0"],"package":"silverstripe/cms","purl":"pkg:composer/silverstripe/cms","source":"GHSA-gm5x-hpmw-xpxg"},{"ecosystem":"Packagist","fixed":["4.4.7"],"introduced":["4.0.0"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-gm5x-hpmw-xpxg"},{"ecosystem":"Packagist","fixed":["4.4.7"],"introduced":["4.0.0"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-gm5x-hpmw-xpxg"},{"ecosystem":"Packagist","fixed":["4.5.4"],"introduced":["4.5.0"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-gm5x-hpmw-xpxg"},{"ecosystem":"Packagist","fixed":["4.5.4"],"introduced":["4.5.0"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-gm5x-hpmw-xpxg"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-6163"},"products":["n/a"],"published":"2020-07-15","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2007-2321","kev_date_added":null,"published":"2007-04-27"},{"cvss_score":9.8,"headline":"Missing warning can lead to unauthenticated admin access in SilverStripe","id":"CVE-2019-12204","kev_date_added":null,"published":"2019-09-25"},{"cvss_score":9.8,"headline":"Silverstripe Framework SQLi Vulnerability","id":"CVE-2019-5715","kev_date_added":null,"published":"2019-04-11"},{"cvss_score":8.8,"headline":"Silverstripe CSRF Protection Bypass via GraphQL","id":"CVE-2019-12437","kev_date_added":null,"published":"2020-02-19"},{"cvss_score":7.5,"headline":"SilverStripe Folders migrated from 3.x may be unsafe to upload to","id":"CVE-2020-9280","kev_date_added":null,"published":"2020-04-15"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2011-4960","kev_date_added":null,"published":"2012-09-17"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can identify SilverStripe hosting via a default URL path, revealing the technology stack without exposing version details.","url":"https://insights.sbomify.com/CVE-2020-6164/"}