CVE-2021-33676
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 · uneditedA missing authority check in SAP CRM, versions - 700, 701, 702, 712, 713, 714, could be leveraged by an attacker with high privileges to compromise confidentiality, integrity, or availability of the system.
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 confidenceMissing authority check vulnerability in SAP CRM versions 700-714 allows authenticated users with high privileges to bypass authorization controls and perform unauthorized operations, potentially compromising confidentiality, integrity, or availability of the affected system.
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= 700= 701= 702= 712= 713= 714CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 CRM versionExecute SAP transaction code SM037 or check system version via SAP transaction code SWTyPful or system report for CRM component version. Alternatively, check SAP Solution Manager or use transaction code SUSG to view installed software components.Affected if The installed SAP CRM version matches exactly 700, 701, 702, 712, 713, or 714.
-
Confirm CRM component is installedCheck if the SAP CRM application component is present in the system by reviewing installed software components via transaction code SE16N (table SWCOMP) or via SAP LMDB.Affected if The CRM application component is installed and running.
-
Verify high-privilege user assignmentsReview user role assignments using transaction code PFCG or SUIM to identify users assigned privileged roles that could exploit the missing authority check.Affected if Users with elevated privileges (such as admin or super-user roles) exist in the system.
-
Check authorization concept configurationExamine whether custom authority checks have been implemented around the vulnerable area. Review authorization objects related to CRM transactions using transaction code SU53 or analyze authorization traces via ST01N.Affected if The system relies on standard SAP CRM authorization objects without additional custom checks, or gaps exist in authority object coverage.
The environment is affected if SAP CRM versions 700, 701, 702, 712, 713, or 714 are installed and the system has users with elevated privileges who could bypass authorization controls.
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 relevant SAP security patch to implement proper authority checks. Additionally, review and restrict privileged user roles to最小权限原则 following SAP security best practices.
- 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-33676 — 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-33676 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