# CVE-2020-6311: Missing authorization in BANKING SERVICES FROM SAP 9.0(Bank Analyzer)

> Authenticated users can escalate privileges and access restricted banking data due to improper authorization checks in SAP banking services.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** 9 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9w4c-84x2-59qr

## What is CVE-2020-6311?

CVE-2020-6311 is a medium-severity missing authorization vulnerability in BANKING SERVICES FROM SAP 9.0(Bank Analyzer), published on 9 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Banking services from SAP 9.0 (Bank Analyzer), version - 500, and SAP S/4HANA for financial products subledger, version � 100, does not correctly perform necessary authorization checks for an authenticated user due to Improper Authorization checks, that may cause a system administrator to create incorrect authorization proposals. This may result in privilege escalation and may expose restricted banking data.

Weakness: CWE-863 (Incorrect Authorization), CWE-285 (Improper Authorization)

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

It affects 2 products.


Products: Sap Bank Analyzer, Sap S\/4hana for Financial Products Subledger.

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

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

## Is CVE-2020-6311 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-6311 is a medium-severity missing authorization vulnerability in BANKING SERVICES FROM SAP 9.0(Bank Analyzer), published on 9 Sep 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-6311 in the wild and no public exploit code.

Affected product: BANKING SERVICES FROM SAP 9.0(Bank Analyzer). 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-6311/ (Markdown: https://insights.sbomify.com/CVE-2020-6311/index.md)
```

## Sources

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

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