dbcve.org
Bank AnalyzerApplication · Sap

CVE-2020-6311

MEDIUM · 6.5 CVSS v3.1 Published 2020-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Improper authorization vulnerability in SAP Bank Analyzer 500 and S/4HANA for financial products subledger allows authenticated users to bypass authorization checks, potentially escalating privileges and exposing restricted banking data through incorrect authorization proposals created by administrators.

MitigationApply SAP security patches/notes for this vulnerability, review and correct authorization roles and proposals in affected banking modules, and implement proper authorization validation for all banking data access paths.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Bank AnalyzerApplication
Affected:= 500
S\/4hana For Financial Products SubledgerWeb browser
Affected:= 100

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SAP Bank Analyzer version
    In SAP GUI, execute transaction SM37 or check system information via transaction SRM0 to determine if SAP Bank Analyzer version 500 is installed. Alternatively, use transaction SPAM to view installed software components and their versions.
    Affected if SAP Bank Analyzer version 500 is installed in the system
  2. Identify SAP S/4HANA for Financial Products Subledger version
    In SAP GUI, execute transaction SPAM or use transaction ST03 to check installed software components. Look for the component 'SAP S/4HANA for Financial Products Subledger' and verify if version 100 is present.
    Affected if SAP S/4HANA for Financial Products Subledger version 100 is installed
  3. Review authorization roles in banking modules
    Use transaction PFCG to review authorization roles assigned to users accessing banking functions. Check role menus for authorization objects related to Bank Analyzer and financial subledger transactions.
    Affected if Users have banking roles but authorization role maintenance shows incorrect or missing authorization proposals
  4. Inspect authorization proposals for banking data
    Use transaction SU24 within the banking transaction codes (such as those in the Bank Analyzer module) to inspect authorization proposal values. Verify if authorization objects have been modified with incorrect or overly permissive values.
    Affected if Authorization proposals in SU24 for banking transactions show non-standard or permissive authorization values that could allow bypass
  5. Check for unrestricted banking data access paths
    Use transaction SUIM to run authorization traces (via ST01) or analyze role assignments for banking-specific transaction codes. Identify if users can access restricted banking data without proper authorization checks.
    Affected if Users can access banking data transactions without proper role-based restrictions or authorization object validation fails

The environment is affected if either SAP Bank Analyzer 500 or SAP S/4HANA for Financial Products Subledger 100 is installed AND banking authorization roles or proposals contain incorrect or permissive configurations that allow bypass of authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SAP security patches/notes for this vulnerability, review and correct authorization roles and proposals in affected banking modules, and implement proper authorization validation for all banking data access paths.

Fix this in Bank Analyzer Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-6311 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-6311 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data