CVE-2020-6199
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 · uneditedThe view FIMENAV_COMPCERT in SAP ERP (MENA Certificate Management), EAPPGLO version 607, SAP_FIN versions- 618, 730 and SAP S/4HANA (MENA Certificate Management), S4CORE versions- 100, 101, 102, 103, 104; does not have any authorization check to it due to which an attacker without an authorization group can maintain any company certificate, 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 confidenceThe FIMENAV_COMPCERT view in SAP ERP and S/4HANA's MENA Certificate Management component lacks proper authorization validation. An attacker can access this view without belonging to an authorized group and can create, modify, or delete company certificates, leading to unauthorized changes to the certificate repository.
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= 607CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify SAP system type and versionExecute transaction 'SM51' or use transaction 'SE11' to view system version information. Check if the system is SAP ERP or S/4HANA and note the version number.Affected if System is SAP ERP or S/4HANA with version matching 607 as specified in the affected versions
-
Verify MENA Certificate Management component is installedUse transaction 'SPAM' or 'SAINT' to check if the MENA Certificate Management component (likely in the SAP_BS_FND or enterprise extension packages) is installed in the system.Affected if The MENA Certificate Management component is installed in the SAP system
-
Confirm FIMENAV_COMPCERT view existsUse transaction 'SE11' or 'SE54' to search for and display the FIMENAV_COMPCERT view in the ABAP Dictionary.Affected if The FIMENAV_COMPCERT view exists in the system dictionary
-
Check authorization object assignments for the viewUse transaction 'SUIM' or 'PFCG' to examine which roles or authorization groups have authorization to access or maintain the FIMENAV_COMPCERT view. Compare against expected authorized user groups.Affected if Users or roles without proper authorization are able to access the FIMENAV_COMPCERT view or unauthorized roles exist for this view
A system is affected if it is SAP ERP or S/4HANA version 607 with the MENA Certificate Management component installed, where the FIMENAV_COMPCERT view is present and accessible to unauthorized users or roles.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the relevant SAP Security Note for CVE-2020-6199 and implement proper authorization checks on the FIMENAV_COMPCERT view to restrict certificate maintenance to authorized users only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2020-6199 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-6199 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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