CVE-2021-21472
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 Software Provisioning Manager 1.0 (SAP NetWeaver Master Data Management Server 7.1) does not have an option to set password during its installation, this allows an authenticated attacker to perform various security attacks like Directory Traversal, Password Brute force Attack, SMB Relay attack, Security Downgrade.
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 confidenceSAP Software Provisioning Manager 1.0 for SAP NetWeaver Master Data Management Server 7.1 lacks a password configuration option during installation. This missing security control allows authenticated attackers to leverage multiple attack vectors including Directory Traversal, Password Brute Force, SMB Relay, and Security Downgrade 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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify SAP Software Provisioning Manager installationCheck the installed version of SAP Software Provisioning Manager in the system. On Windows, this may be visible in Add/Remove Programs or the SAP installer logs. On Unix/Linux, check the SAP installation directory structure for provisioning manager components.Affected if The installed version is SAP Software Provisioning Manager 1.0 (exact version 1.0) for SAP NetWeaver Master Data Management Server 7.1
-
Verify password configuration during installationReview the installation logs or configuration files created during the SAP Software Provisioning Manager installation. Look for any password-related settings or the absence thereof in the provisioning manager configuration.Affected if No password configuration option was presented or configured during the installation process, or default/blank passwords are in use
-
Check for SMB and network authentication exposureExamine network listening services and SMB configurations on the server where the provisioning manager is installed. Check if SMB signing is disabled or if the server accepts authentication over unencrypted channels.Affected if SMB signing is disabled or the server accepts authentication on ports 445/139 without proper security controls, indicating vulnerability to SMB Relay or Security Downgrade attacks
-
Review authentication logs for brute force attemptsExamine authentication logs, SAP system logs, and security event logs for patterns of repeated failed login attempts or password guessing activity targeting the provisioning manager.Affected if Logs show evidence of brute force attempts or unusual authentication patterns targeting the provisioning manager interface
A user is affected if SAP Software Provisioning Manager version 1.0 is installed and no password was configured during installation, leaving the system exposed to the described attack vectors.
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 the vendor patch from SAP once available. In the interim, implement network segmentation, restrict access to the provisioning manager, and monitor for signs of the described attack patterns.
- Consultation8.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21472 — 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-21472 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