CVE-2021-33671
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 Guided Procedures (Administration Workset), versions - 7.10, 7.20, 7.30, 7.31, 7.40, 7.50, does not perform necessary authorization checks for an authenticated user, resulting in escalation of privileges. The impact of missing authorization could result to abuse of functionality restricted to a particular user group, and could allow unauthorized users to read, modify or delete restricted 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 confidenceSAP NetWeaver Guided Procedures (Administration Workset) versions 7.10-7.50 lacks proper authorization checks for authenticated users, allowing privilege escalation to access functionality and data restricted to specific user groups.
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= 7.20= 7.30= 7.31= 7.40= 7.50CVSS 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.
-
Verify SAP NetWeaver Guided Procedures is installedIn the SAP system, navigate to System > Status or use transaction code SM37 to check installed software components. Look for component 'Guided Procedures' or 'EP-GUIDEDPROC' in the installed software catalog.Affected if The Guided Procedures component is listed as installed in the SAP system
-
Check the installed Guided Procedures versionUse SAP transaction code SAINT (SAP Installation Tool) or SMICM (Internet Communication Manager) to view installed product versions. Locate the Guided Procedures version number and compare it exactly to 7.10, 7.20, 7.30, 7.31, 7.40, or 7.50.Affected if The installed version matches exactly 7.10, 7.20, 7.30, 7.31, 7.40, or 7.50
-
Verify if Administration Workset is configuredIn SAP NetWeaver Administrator (NWA), navigate to Operations > Systems > System Landscape > Components. Look for the Administration Workset component under Guided Procedures configuration, or use transaction code NWA > Configuration > Guided Procedures Administration.Affected if The Administration Workset is deployed and active in the Guided Procedures environment
-
Review user authorization role assignmentsUse transaction code PFCG (Role Maintenance) to examine roles assigned to users who have access to Guided Procedures. Check whether standard user roles have been granted elevated administrative privileges that should be restricted to specific user groups.Affected if Authenticated users without elevated group membership can access administrative functions through Guided Procedures
A system is affected if SAP NetWeaver Guided Procedures versions 7.10 through 7.50 is installed with the Administration Workset enabled and users can access restricted functionality beyond their assigned authorization group.
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.
dbcve · scopedApply the relevant SAP security patch for CVE-2021-33671 and review/strengthen authorization role assignments in the affected SAP system.
- 1. Access the SAP Support Portal at support.sap.com/patches using your S-user ID
- 2. Search for SAP Security Note related to CVE-2021-33671 (typically identified by an SAP Note number)
- 3. Download and implement the security patch as instructed in the SAP Note
- 4. Apply the patch following SAP's standard patch deployment procedures
- 5. Verify the authorization controls are properly enforced after patch application
- 6. Test that users can only access functionality permitted by their assigned roles
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33671 — 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-33671 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