CVE-2020-6191
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 · uneditedSAP Landscape Management, version 3.0, allows an attacker with admin privileges to execute malicious executables with root privileges in SAP Host Agent via SAP Landscape Management due to Missing Input Validation.
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 confidenceThis is a privilege escalation vulnerability in SAP Landscape Management 3.0 where an attacker with admin privileges can bypass input validation to execute malicious executables with root privileges through the SAP Host Agent component. The missing input validation allows arbitrary command execution at the root level.
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= 3.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SAP Landscape Management versionUse SAP LM command line tools or check installed packages to retrieve the exact version number of SAP Landscape ManagementAffected if Version is exactly 3.0 (no other versions are listed as affected)
-
Verify SAP Host Agent component presenceCheck if the SAP Host Agent component is installed and running as part of the SAP Landscape Management deploymentAffected if SAP Host Agent is present and active in the environment
-
Review admin user access controlsAudit the list of users granted admin-level privileges within SAP Landscape Management to confirm only authorized personnel have accessAffected if Any admin-level accounts exist in the system (this is a prerequisite for exploitation)
-
Inspect command execution logsReview SAP Host Agent logs and system audit logs for any suspicious or unauthorized command executions, particularly those involving system-level or root-privileged operationsAffected if Unusual root-level commands are found in logs that were not initiated by authorized administrators
-
Check for custom executable configurationsExamine SAP Landscape Management configuration files and settings related to executable execution, looking for any non-standard or user-defined executable pathsAffected if Custom or unauthorized executable paths are configured within SAP Landscape Management settings
The environment is affected if SAP Landscape Management version 3.0 is running with SAP Host Agent enabled and any admin accounts exist, as these conditions enable the privilege escalation path.
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 SAP security patch for CVE-2020-6191 and implement proper input validation on all user-supplied parameters within SAP Landscape Management to prevent unauthorized executable execution.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6191 — 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-6191 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