{"answers":{"affected":"5 open source packages ship an affected version, including silverstripe/graphql, silverstripe and silverstripe/recipe-cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-6165 in the wild and no public exploit code.","fix":"Upgrade silverstripe/graphql to 3.2.4 or later.","what":"CVE-2020-6165 is a medium-severity missing authorization 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-6165 and fix it if it is affected.\n\nWhat it is: CVE-2020-6165 is a medium-severity missing authorization 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-6165 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/graphql (Packagist): affected from 3.2.0; fixed in 3.2.4\n- silverstripe/graphql (Packagist): affected from 3.2.0; fixed in 3.2.4\n- silverstripe (Bitnami): affected from 3.2.0; fixed in 3.2.4, 3.3.0, 4.5.3\n- silverstripe/recipe-cms (Packagist): affected from 4.5.0; fixed in 4.5.3\n- silverstripe/recipe-cms (Packagist): affected from 4.5.0; fixed in 4.5.3\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-6165/ (Markdown: https://insights.sbomify.com/CVE-2020-6165/index.md)","id":"CVE-2020-6165","markdown":"https://insights.sbomify.com/CVE-2020-6165/index.md","name":"CVE-2020-6165","record":{"aliases":["BIT-silverstripe-2020-6165","GHSA-589q-75r3-mfq4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SilverStripe CMS","requires_auth":"none","summary":"Authenticated users can read unauthorized records via GraphQL endpoints due to flawed permission checks in SilverStripe CMS.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"silverstripe","vendor":"silverstripe"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"SilverStripe 4.5.0 allows attackers to read certain records that should not have been placed into a result set. This affects silverstripe/recipe-cms. The automatic permission-checking mechanism in the silverstripe/graphql module does not provide complete protection against lists that are limited (e.g., through pagination), resulting in records that should have failed a permission check being added to the final result set. GraphQL endpoints are configured by default (e.g., for assets), but the admin/graphql endpoint is access protected by default. This limits the vulnerability to all authenticated users, including those with limited permissions (e.g., where viewing records exposed through admin/graphql requires administrator permissions). However, if custom GraphQL endpoints have been configured for a specific implementation (usually under /graphql), this vulnerability could also be exploited through unauthenticated requests. This vulnerability only applies to reading records; it does not allow unauthorised changing of records.","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 has Incorrect Default Permissions","id":"CVE-2020-6165","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"silverstripe:silverstripe","products":["silverstripe:silverstripe"],"type":"missing_authorization","year":"2020"},"n_packages":5,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2020-6166"},"packages":[{"ecosystem":"Bitnami","fixed":["3.2.4","3.3.0","4.5.3"],"introduced":["3.2.0","3.2.5","4.5.0"],"last_affected":[],"package":"silverstripe","purl":"pkg:bitnami/silverstripe","source":"BIT-silverstripe-2020-6165"},{"ecosystem":"Packagist","fixed":["3.2.4"],"introduced":["3.2.0"],"last_affected":[],"package":"silverstripe/graphql","purl":null,"source":"GHSA-589q-75r3-mfq4"},{"ecosystem":"Packagist","fixed":["3.2.4"],"introduced":["3.2.0"],"last_affected":[],"package":"silverstripe/graphql","purl":"pkg:composer/silverstripe/graphql","source":"GHSA-589q-75r3-mfq4"},{"ecosystem":"Packagist","fixed":["4.5.3"],"introduced":["4.5.0"],"last_affected":[],"package":"silverstripe/recipe-cms","purl":null,"source":"GHSA-589q-75r3-mfq4"},{"ecosystem":"Packagist","fixed":["4.5.3"],"introduced":["4.5.0"],"last_affected":[],"package":"silverstripe/recipe-cms","purl":"pkg:composer/silverstripe/recipe-cms","source":"GHSA-589q-75r3-mfq4"}],"prev":{"headline":"Silverstripe CMS information disclosure","id":"CVE-2020-6164"},"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 CMS information disclosure","id":"CVE-2020-6164","kev_date_added":null,"published":"2020-07-15"},{"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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":"Authenticated users can read unauthorized records via GraphQL endpoints due to flawed permission checks in SilverStripe CMS.","url":"https://insights.sbomify.com/CVE-2020-6165/"}