dbcve.org
Landscape TransformationApplication · Sap

CVE-2021-38176

HIGH · 8.8 CVSS v3.1 Published 2021-09-14
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
Due to improper input sanitization, an authenticated user with certain specific privileges can remotely call NZDT function modules listed in Solution Section to execute manipulated query or inject ABAP code to gain access to Backend Database. On successful exploitation the threat actor could completely compromise confidentiality, integrity, and availability of the system.

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

This is an input validation vulnerability in SAP NetWeaver Diagnostic Tool (NZDT) function modules. Improper input sanitization allows authenticated users with specific privileges to execute manipulated database queries or inject ABAP code, leading to unauthorized backend database access and potential complete system compromise.

MitigationImplement rigorous input validation and sanitization for all user-supplied parameters in NZDT function modules, and apply principle of least privilege to restrict which users can access these functions.

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
Landscape TransformationApplication
Affected:= 2.0
Landscape Transformation Replication ServerApplication
Affected:= 1.0= 2.0= 3.0
S\/4hanaApplication
Affected:= 1511= 1610= 1709= 1809= 1909= 2020= 2021
Test Data Migration ServerApplication
Affected:= 4.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
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 if NetWeaver Diagnostic Tool (NZDT) is installed
    In SAP system, access transaction code /n/SAPETD/MAIN or check for package SAPETD in transaction SE80. Alternatively, query table TADIR for objects in namespace /SAPETD/.
    Affected if The NZDT package SAPETD exists in the system, indicating the diagnostic tool is present.
  2. Verify the installed SAP component versions
    Execute ABAP report RSUSR200 to check installed software components, or use transaction SM37 to view system version info. Check SAP S/4HANA release via transaction SNOTE or system report. For SAP LT Replication Server, check via transaction LTR. For TDMS, check via transaction SDTM_INFO.
    Affected if Installed versions match: SAP LT 2.0, SAP LT Replication Server 1.0/2.0/3.0, SAP S/4HANA 1511/1610/1709/1809/1909/2020/2021, or TDMS 4.0.
  3. Check for exposed NZDT function modules
    Query transaction SE37 or SE80 for function modules in function group /SAPETD/FG_DIAG or similar NZDT groups. Use transaction SE11 to inspect table TFDIR for function module names containing /SAPETD/ or NETWEAVER_DIAGNOSTIC.
    Affected if Function modules from NZDT are present and accessible in the system.
  4. Identify users with NZDT privileges
    Use transaction SUIM to check for roles containing authorization object S_RFC with activity 16 (execute) for RFC destination /SAP/ETD* or roles assigned to profile SAP_ETD_*. Check transaction PFCG for roles containing authorization for transaction /n/SAPETD/.
    Affected if Users or roles have execute privileges on NZDT function modules or transaction /n/SAPETD/ is available to authenticated users.
  5. Audit recent NZDT function module executions
    Review transaction ST03N for RFC calls to function modules in /SAPETD/ namespace. Check transaction SM37 for background jobs executing NZDT-related programs. Query table JDRSKEPH for execution logs if audit logging is enabled.
    Affected if There are logged executions of NZDT function modules, indicating the feature is being actively used.

A system is affected if it has SAP NetWeaver Diagnostic Tool (NZDT) installed and exposes function modules to authenticated users with execute privileges, particularly on vulnerable SAP S/4HANA, SAP LT, or TDMS versions.

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

Implement rigorous input validation and sanitization for all user-supplied parameters in NZDT function modules, and apply principle of least privilege to restrict which users can access these functions.

Fix this in Landscape Transformation Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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