Adaptive ExtensionsPlugin / extension · Sap

CVE-2020-6236

HIGH · 7.2 CVSS v3.1 Published 2020-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
SAP Landscape Management, version 3.0, and SAP Adaptive Extensions, version 1.0, allows an attacker with admin_group privileges to change ownership and permissions (including S-user ID bit s-bit) of arbitrary files remotely. This results in the possibility to execute these files as root user from a non-root context, leading to Privilege Escalation.

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

SAP Landscape Management 3.0 and SAP Adaptive Extensions 1.0 contain a privilege escalation vulnerability where an authenticated attacker with admin_group privileges can change ownership and permissions (including SUID bits) of arbitrary files remotely. This allows execution of those files as root from a non-root context, enabling complete system compromise.

MitigationApply the available SAP security patch for CVE-2020-6236. Restrict admin_group privileges to minimum necessary personnel and audit all privileged accounts for signs of compromise.

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
Adaptive ExtensionsPlugin / extension
Affected:= 1.0
Landscape ManagementApplication
Affected:= 3.0

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
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 checks

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

  1. Identify installed SAP Landscape Management version
    Query the SAP system for the installed version of SAP Landscape Management (e.g., via SAP LM installer, SAP Support Portal, or SAP system information files)
    Affected if Version is exactly 3.0 (the specific affected version)
  2. Identify installed SAP Adaptive Extensions version
    Query the SAP system for the installed version of SAP Adaptive Extensions (check SAP component metadata or version files in the SAP directory structure)
    Affected if Version is exactly 1.0 (the specific affected version)
  3. Check for admin_group privilege assignment
    Review user account privileges within the SAP Landscape Management system to determine if any account has admin_group permissions assigned
    Affected if Any user account possesses admin_group privileges in the SAP system
  4. Audit for unauthorized SUID files
    Scan the operating system for SUID files in unexpected locations, particularly outside standard SAP binary directories, using commands like 'find / -perm -4000 2>/dev/null'
    Affected if New or unexpected SUID files appear on the system, especially for binaries that should not have elevated privileges
  5. Review file ownership and permission change logs
    Check SAP Landscape Management audit logs and system audit logs for file ownership or permission modifications, particularly involving root-owned files
    Affected if Evidence exists of unauthorized ownership or permission changes on system files

A user is affected if their environment runs SAP Landscape Management 3.0 or SAP Adaptive Extensions 1.0 and any account with admin_group privileges exists, as the vulnerability allows privilege escalation through arbitrary file permission manipulation.

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 available SAP security patch for CVE-2020-6236. Restrict admin_group privileges to minimum necessary personnel and audit all privileged accounts for signs of compromise.

Fix this in Adaptive Extensions Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-6236 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