dbcve.org
ErpApplication · Sap

CVE-2020-6188

HIGH · 8.8 CVSS v3.1 Published 2020-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
VAT Pro-Rata reports in SAP ERP (SAP_APPL versions 600, 602, 603, 604, 605, 606, 616 and SAP_FIN versions 617, 618, 700, 720, 730) and SAP S/4 HANA (versions 100, 101, 102, 103, 104) do not perform necessary authorization checks for an authenticated user leading to Missing Authorization Check.

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 · high confidence

CVE-2020-6188 is a missing authorization check vulnerability in VAT Pro-Rata reports within SAP ERP (SAP_APPL and SAP_FIN versions) and SAP S/4HANA. An authenticated user can access these financial reports without proper authorization, potentially exposing sensitive VAT-related tax data to unauthorized parties.

MitigationApply the relevant SAP security patches for CVE-2020-6188. If patches are unavailable, implement compensating controls by restricting access to VAT Pro-Rata reports through SAP role-based access control (GRC) configurations.

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
ErpApplication
Affected:= 6.0
S\/4 HanaApplication
Affected:= 1511= 1610= 1709= 1809= 1909

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
High
Availability
High

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

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 installed SAP product and version
    Use transaction code 'SM51' to view the SAP system version, or check system information via 'SID$'. For SAP S/4HANA, verify the version number (e.g., 1511, 1610, 1709, 1809, 1909). For SAP ERP, verify if it is version 6.0.
    Affected if The installed version is SAP ERP 6.0, or SAP S/4HANA versions 1511, 1610, 1709, 1809, or 1909.
  2. Confirm VAT Pro-Rata reports exist in the system
    Search for VAT Pro-Rata related reports using transaction code 'SE38' or 'SA38' with keywords like 'PRO-RATA' or 'VAT PRORATA'. Check if any report programs with these terms are present in the system.
    Affected if VAT Pro-Rata report programs exist in the system and are accessible to users.
  3. Check user access to VAT Pro-Rata reports
    Use transaction code 'SUIM' (User Information System) to search for users who have profiles or roles containing access to VAT Pro-Rata reports. Alternatively, check transaction code 'PFCG' for role definitions.
    Affected if Users without proper authorization can access or execute VAT Pro-Rata reports.
  4. Verify authorization objects for VAT Pro-Rata reports
    Use transaction code 'SU53' immediately after a user attempts to access VAT Pro-Rata reports to check which authorization objects failed. Also review role assignments via 'PFCG' to see if proper authorization objects (such as F_TAXREP) are configured.
    Affected if Users can access the reports without the required authorization object checks passing, or no specific authorization objects are assigned to restrict access.

The environment is affected if it runs SAP ERP 6.0 or SAP S/4HANA versions 1511 through 1909, and users can access VAT Pro-Rata reports without proper authorization role restrictions.

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 the relevant SAP security patches for CVE-2020-6188. If patches are unavailable, implement compensating controls by restricting access to VAT Pro-Rata reports through SAP role-based access control (GRC) configurations.

Fix this in Erp Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-6188 — 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-6188 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