dbcve.org
ErpApplication · Sap

CVE-2020-6212

MEDIUM · 5.4 CVSS v3.1 Published 2020-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/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
Egypt localized withholding tax reports Clearing of Liabilities and Remittance Statement and Summary in SAP ERP (versions 618, 730, EAPPLGLO 607) and S/4 HANA (versions 100, 101, 102, 103, 104) do not perform necessary authorization checks for an authenticated user, allowing reading or modification of some tax reports, due 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 · moderate confidence

Missing authorization check in Egypt-localized withholding tax reporting components (Clearing of Liabilities and Remittance Statement/Summary) in SAP ERP (versions 618, 730, EAPPLGLO 607) and S/4HANA (versions 100-104). Authenticated users can read or modify tax reports without proper authorization, allowing unauthorized access to sensitive tax data.

MitigationApply SAP security notes addressing this authorization flaw and review/configure role-based access controls (PFCG roles) for affected tax reporting transactions to enforce proper authorization checks.

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:= 607= 618= 730
S\/4hanaApplication
Affected:= 100= 101= 102= 103= 104

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 product and version
    Execute transaction SM51 to display the SAP System information, or check the SAP system version via system profile parameters or transaction SXMB_MONI for release information.
    Affected if The product is SAP ERP versions 607, 618, or 730, or S/4HANA versions 100-104.
  2. Verify Egypt localization is active
    Check if the country version for Egypt is installed via transaction SE16N on table T001 (company codes) with land1 = 'EG', or check via transaction OX02 (country version).
    Affected if Egypt localization (country code EG) is configured in the SAP system.
  3. Identify affected tax reporting transactions
    Look for transactions related to Egypt withholding tax reporting: typically transaction codes for Clearing of Liabilities (e.g., FBN1C or custom Egypt tax transactions) and Remittance Statement/Summary. Check transaction SU03 for authorization objects related to tax reporting.
    Affected if The system contains or uses Egypt-localized withholding tax reporting transactions (Clearing of Liabilities and Remittance Statement/Summary).
  4. Review user authorization roles
    Execute transaction PFCG to review roles assigned to users. Check if roles granted for Egypt tax reporting transactions lack proper tax authorization objects (such as F_BKPF_BUK for accounting document authorization or F_TAXWHT for withholding tax).
    Affected if Users have roles granting access to Egypt tax reporting transactions without appropriate tax authorization objects or with excessive privileges.
  5. Check for unauthorized tax data access
    Use transaction ST03N or audit logs (transaction RSAUD) to review recent access to Egypt tax reporting transactions. Query tables like BKPF and BSEG for Egypt company codes and tax-related document types.
    Affected if Users have accessed or modified Egypt withholding tax reports without proper authorization records in the role configuration.

A user is affected if they run SAP ERP (607/618/730) or S/4HANA (100-104) with Egypt localization enabled and have users with roles granting access to Egypt withholding tax reporting components (Clearing of Liabilities and Remittance Statement/Summary) that lack proper tax-specific authorization objects.

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 notes addressing this authorization flaw and review/configure role-based access controls (PFCG roles) for affected tax reporting transactions to enforce proper authorization checks.

Fix this in Erp Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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