Netweaver Master Data ManagementApplication · Sap

CVE-2021-21469

HIGH · 7.5 CVSS v3.1 Published 2021-01-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
When security guidelines for SAP NetWeaver Master Data Management running on windows have not been thoroughly reviewed, it might be possible for an external operator to try and set custom paths in the MDS server configuration. When no adequate protection has been enforced on any level (e.g., MDS Server password not set, network and OS configuration not properly secured, etc.), a malicious user might define UNC paths which could then be exploited to put the system at risk using a so-called SMB relay attack and obtain highly sensitive data, which leads to Information Disclosure.

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

In SAP NetWeaver Master Data Management on Windows, inadequate security guidelines allow an external operator to set custom paths in the MDS server configuration. When protections are insufficient (no MDS password, unsecure network/OS configuration), attackers can define UNC paths to perform SMB relay attacks and obtain highly sensitive data, resulting in information disclosure.

MitigationSet a strong MDS server password and thoroughly review security guidelines for network and OS configuration to prevent unauthorized path configuration and SMB relay attacks.

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
Netweaver Master Data ManagementApplication
Affected:= 7.10= 7.10.750= 710

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the installed SAP NetWeaver MDM version
    Use SAP transaction MDMA or check the SAP MDG/MDM installation files to determine the exact version number. Compare against the affected versions: 7.10, 7.10.750, and 710.
    Affected if The installed version matches 7.10, 7.10.750, or 710 exactly.
  2. Verify if MDS server password is configured
    Access the SAP MDM Configuration or use transaction MDMC to check whether a password has been set for the MDS server. An unset or empty password indicates insufficient protection.
    Affected if No MDS server password is configured or the password is left blank.
  3. Inspect MDS server configuration for custom path settings
    Access the MDM Server configuration interface (via MDMA or MDM Administration) and review the path settings where custom directories can be defined.
    Affected if Custom path configuration options are accessible without proper authentication or there are configured paths that were not set by an administrator.
  4. Review network and OS security configuration
    Examine the Windows host and network configuration where MDM is installed. Check for SMB signing disabled, lack of network segmentation, or other unsecure network/OS settings.
    Affected if Network or OS security hardening is missing or inadequate for the MDM server.

A user is affected if running version 7.10, 7.10.750, or 710 AND the MDS server lacks a password AND custom path configuration is accessible, allowing potential SMB relay attack vectors.

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

Set a strong MDS server password and thoroughly review security guidelines for network and OS configuration to prevent unauthorized path configuration and SMB relay attacks.

Fix this in Netweaver Master Data Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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