CVE-2021-21482
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 NetWeaver Master Data Management, versions - 710, 710.750, allows a malicious unauthorized user with access to the MDM Server subnet to find the password using a brute force method. If successful, the attacker could obtain access to highly sensitive data and MDM administrative privileges leading to information disclosure vulnerability thereby affecting the confidentiality and integrity of the application. This happens when security guidelines and recommendations concerning administrative accounts of an SAP NetWeaver Master Data Management installation have not been thoroughly reviewed.
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 confidenceSAP NetWeaver Master Data Management versions 710 and 710.750 contains a vulnerability allowing an unauthorized user with network access to the MDM Server subnet to perform brute force attacks against administrative accounts. Successful exploitation grants access to highly sensitive data and MDM administrative privileges, resulting in information disclosure and privilege escalation.
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= 7.10.750= 710CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
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 if SAP NetWeaver MDM is runningCheck running processes or services for SAP MDM components, or query the SAP system for installed products using SAP transaction SE84 or SM37 for MDM-related jobsAffected if SAP NetWeaver Master Data Management software is installed and running
-
Determine the installed MDM versionAccess SAP MDM administrative console or check installed product version via SAP transaction SM51, or inspect SAP MDMWIZARD configuration files if accessibleAffected if The version is 7.10, 7.10.750, or 710 (exact match to affected versions)
-
Verify network accessibility of MDM ServerIdentify open ports typically used by MDM (like 50000-50004 for RFC/HTTP) and test connectivity from external/untrusted networks using tools like telnet, nmap, or netcatAffected if The MDM Server ports are reachable from networks outside the trusted MDM Server subnet without authentication barriers
-
Confirm administrative accounts existReview MDM user administration settings via SAP transaction SU01 or MDM Console user management to verify administrative accounts are configuredAffected if Administrative accounts are present in the MDM system (prerequisite for brute force target)
-
Check for account lockout policy enforcementReview MDM security configuration or SAP profile parameters for failed login lockout settings using transaction RZ10 or security audit logsAffected if No account lockout policy is configured or enforced for MDM administrative accounts
A user is affected if they run SAP NetWeaver MDM versions 7.10 or 7.10.750 with the server accessible from an unauthorized network and without account lockout protections in place.
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 dataImplement account lockout policies and enforce strong password policies for administrative accounts following SAP security guidelines. Restrict network access to the MDM Server subnet and consider implementing multi-factor authentication for administrative access.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21482 — 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-21482 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