{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-6265 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-6265 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-6265 is a critical vulnerability in SAP Commerce, published on 9 Jun 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-6265 and fix it if it is affected.\n\nWhat it is: CVE-2020-6265 is a critical vulnerability in SAP Commerce, published on 9 Jun 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-6265 in the wild and no public exploit code.\n\nAffected product: SAP Commerce. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-6265/ (Markdown: https://insights.sbomify.com/CVE-2020-6265/index.md)","id":"CVE-2020-6265","markdown":"https://insights.sbomify.com/CVE-2020-6265/index.md","name":"CVE-2020-6265","record":{"aliases":["GHSA-cqwc-4m4r-gw28"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"SAP Commerce","requires_auth":"none","summary":"Attackers can bypass authentication and authorization in SAP Commerce due to hardcoded credentials, potentially gaining unauthorized access.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"sap","cpe":[{"product":"commerce","vendor":"sap"},{"product":"commerce_data_hub","vendor":"sap"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"SAP Commerce, versions - 6.7, 1808, 1811, 1905, and SAP Commerce (Data Hub), versions - 6.7, 1808, 1811, 1905, allows an attacker to bypass the authentication and/or authorization that has been configured by the system administrator due to the use of Hardcoded Credentials.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hardcoded credentials in SAP Commerce","id":"CVE-2020-6265","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Open redirect in SAP Fiori for SAP S/4HANA","id":"CVE-2020-6266"},"packages":[],"prev":{"headline":"Information disclosure in SAP Commerce","id":"CVE-2020-6264"},"products":["SAP Commerce","SAP Commerce (Data Hub)"],"published":"2020-06-09","related":[{"cvss_score":9.9,"headline":"Code injection in SAP Commerce","id":"CVE-2021-27602","kev_date_added":null,"published":"2021-04-13"},{"cvss_score":9.9,"headline":"Code injection in SAP Commerce","id":"CVE-2021-21477","kev_date_added":null,"published":"2021-02-09"},{"cvss_score":9.8,"headline":"SQL injection in SAP Commerce","id":"CVE-2021-42064","kev_date_added":null,"published":"2021-12-14"},{"cvss_score":8.8,"headline":"Open redirect in SAP Commerce","id":"CVE-2022-41204","kev_date_added":null,"published":"2022-10-11"},{"cvss_score":8.8,"headline":"Missing authorization in SAP Commerce","id":"CVE-2021-40502","kev_date_added":null,"published":"2021-11-10"},{"cvss_score":8.6,"headline":"Information disclosure in SAP Commerce","id":"CVE-2020-6264","kev_date_added":null,"published":"2020-06-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":["SAP SE"]},"summary":"Attackers can bypass authentication and authorization in SAP Commerce due to hardcoded credentials, potentially gaining unauthorized access.","url":"https://insights.sbomify.com/CVE-2020-6265/"}