CVE-2021-21475
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 · uneditedUnder specific circumstances SAP Master Data Management, versions - 710, 710.750, allows an unauthorized attacker to exploit insufficient validation of path information provided by users, thus characters representing 'traverse to parent directory' are passed through to the file APIs. Due to this Directory Traversal vulnerability the attacker could read content of arbitrary files on the remote server and expose sensitive data.
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 confidenceDirectory Traversal vulnerability in SAP Master Data Management (versions 710, 710.750) allows unauthorized attackers to read arbitrary files on the server by exploiting insufficient validation of path information. User-supplied input containing path traversal sequences (e.g., ../) is passed through to file APIs without proper sanitization, enabling access to sensitive files outside the intended directory.
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= 710= 710.750CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed SAP MDM versionQuery the SAP Netweaver system for the Master Data Management component version using SAP transaction codes (e.g., SM37 for jobs, or check via SAPMMC snap-in), or inspect version information in SAP MDM installation directories if accessibleAffected if Installed version is 710 or 710.750 exactly
-
Confirm MDM server component is deployedCheck if the SAP Master Data Management Server component is installed and running on the system. This may be visible in SAP management consoles or Windows services related to SAP MDMAffected if MDM Server component is present and running
-
Determine if MDM HTTP/HTTPS endpoints are accessibleCheck network configuration or firewall rules to see if ports used by SAP MDM (typically HTTP/HTTPS ports configured during MDM setup) are open and reachableAffected if MDM HTTP/HTTPS endpoints are exposed on the network without proper access restrictions
-
Verify no input validation filter exists for path traversalReview any web application firewall (WAF), reverse proxy rules, or application-level input validation configurations protecting MDM endpoints for blocks on ../ sequences or path traversal patternsAffected if No filter or validation is in place to block path traversal characters in MDM input
You are affected if your SAP Netweaver Master Data Management Server is version 710 or 710.750 and the MDM endpoints are network-accessible without input validation filters blocking path traversal sequences.
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 vendor-supplied patch for CVE-2021-21475; until then, restrict access to affected MDM endpoints and implement input validation filters to block path traversal characters.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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,024.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21475 — 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-2021-21475 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