# CVE-2020-6264: Information disclosure in SAP Commerce

> An attacker can access restricted information in SAP Commerce, leading to information disclosure.

- **Severity:** High 8.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mwr9-4jvv-9cxv

## What is CVE-2020-6264?

CVE-2020-6264 is a high-severity vulnerability in SAP Commerce, published on 10 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SAP Commerce, versions - 6.7, 1808, 1811, 1905, may allow an attacker to access information under certain conditions which would otherwise be restricted, leading to Information Disclosure.

## Which versions are affected by CVE-2020-6264?

It affects 1 product.


Products: Sap Commerce.

## How do I fix CVE-2020-6264?

No fix has been published for CVE-2020-6264 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-6264 being exploited?

There is no known exploitation of CVE-2020-6264 in the wild and no public exploit code.

## Other vulnerabilities in SAP Commerce

- [CVE-2021-27602](https://insights.sbomify.com/CVE-2021-27602/): Code injection in SAP Commerce (critical 9.9)
- [CVE-2021-21477](https://insights.sbomify.com/CVE-2021-21477/): Code injection in SAP Commerce (critical 9.9)
- [CVE-2021-42064](https://insights.sbomify.com/CVE-2021-42064/): SQL injection in SAP Commerce (critical 9.8)
- [CVE-2020-6265](https://insights.sbomify.com/CVE-2020-6265/): Hardcoded credentials in SAP Commerce (critical 9.8)
- [CVE-2022-41204](https://insights.sbomify.com/CVE-2022-41204/): Open redirect in SAP Commerce (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6264 and fix it if it is affected.

What it is: CVE-2020-6264 is a high-severity vulnerability in SAP Commerce, published on 10 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6264 in the wild and no public exploit code.

Affected product: SAP Commerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-6264/ (Markdown: https://insights.sbomify.com/CVE-2020-6264/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-6264
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-6264
- OSV: https://osv.dev/vulnerability/CVE-2020-6264

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-6264/
Summaries are generated and may contain mistakes; the official description above is the record.