# CVE-2020-6297: Information disclosure in SAP Data Intelligence

> An attacker can access restricted confidential system configuration information during the upgrade from SAP Data Hub to SAP Data Intelligence.

- **Severity:** Medium 6.3 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m7w2-7qrq-qfcf

## What is CVE-2020-6297?

CVE-2020-6297 is a medium-severity vulnerability in SAP Data Intelligence, published on 12 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Under certain conditions the upgrade of SAP Data Hub 2.7 to SAP Data Intelligence, version - 3.0, allows an attacker to access confidential system configuration information, that should otherwise be restricted, leading to Information Disclosure.

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

It affects 1 product.


Products: Sap Data Intelligence.

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

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

## Is CVE-2020-6297 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-6297 is a medium-severity vulnerability in SAP Data Intelligence, published on 12 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6297 in the wild and no public exploit code.

Affected product: SAP Data Intelligence. 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-6297/ (Markdown: https://insights.sbomify.com/CVE-2020-6297/index.md)
```

## Sources

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

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