Vulnerability in SAP Commerce
CVE-2020-6302
SAP Commerce versions 6.7, 1808, 1811, 1905, 2005 contains the jSession ID in the backoffice URL when the application is loaded initially. An attacker can get this session ID via shoulder surfing or man in the middle attack and subsequently get access to admin user accounts, leading to Session Fixation and complete compromise of the confidentiality, integrity and availability of the application.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.1 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS: 0.008 (56.3th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 56th percentile — 56.3% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.008 · newest: 0.008 · change: 0.000
Affected products
- SAP Commerce — versions 6.7, 1808, 1811
- SAP Se Commerce — versions < 6.7, < 1808, < 1811
Weakness classification (CWE)
Public proof-of-concept exploits
References
- wiki.scn.sap.com/wiki/pages/viewpage.action (Vendor Advisory)
- launchpad.support.sap.com/ (Permissions Required)
Frequently asked questions
- What is CVE-2020-6302?
- CVE-2020-6302 is a high-severity vulnerability in SAP Commerce, classified under Session Fixation. CVSS score: 8.1/10. Published 2020-09-09.
- How severe is CVE-2020-6302?
- High severity. CVSS v3 base score is 8.1 out of 10.
- Is CVE-2020-6302 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.