# CVE-2020-6204: Missing authorization in SAP Treasury and Risk Management (Transaction Management) (EA-FINSERV)

> Attackers can view unauthorized contract records in SAP Treasury due to a missing authorization check in selection queries.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-whqr-v2xf-6j78

## What is CVE-2020-6204?

CVE-2020-6204 is a medium-severity missing authorization vulnerability in SAP Treasury and Risk Management (Transaction Management) (EA-FINSERV), published on 10 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The selection query in SAP Treasury and Risk Management (Transaction Management) (EA-FINSERV?versions 600, 603, 604, 605, 606, 616, 617, 618, 800 and S4CORE versions 101, 102, 103, 104) returns more records than it should be when selecting and displaying the contract number, leading to Missing Authorization Check.

Weakness: CWE-862 (Missing Authorization)

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

It affects 2 products.


Products: Sap Treasury and Risk Management \(Ea-Finserv\), Sap Treasury and Risk Management \(S4core\).

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

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

## Is CVE-2020-6204 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-6204 is a medium-severity missing authorization vulnerability in SAP Treasury and Risk Management (Transaction Management) (EA-FINSERV), published on 10 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6204 in the wild and no public exploit code.

Affected product: SAP Treasury and Risk Management (Transaction Management) (EA-FINSERV). 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-6204/ (Markdown: https://insights.sbomify.com/CVE-2020-6204/index.md)
```

## Sources

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

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