CVE-2022-29611
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 Application Server for ABAP and ABAP Platform do not perform necessary authorization checks for an authenticated user, resulting in escalation of privileges.
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 NetWeaver Application Server for ABAP and ABAP Platform contains a missing authorization check vulnerability. An authenticated user can bypass proper authorization controls to escalate privileges to higher-level functions or roles they are not entitled to access.
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= 710= 711= 730= 731= 740= 750= 751= 752= 753CVSS 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.
-
Determine installed ABAP versionExecute transaction SM51 or use the SAP GUI version information to identify the NetWeaver AS ABAP release version (e.g., 700, 750, 753).Affected if The installed version matches any of these: 700, 701, 702, 710, 711, 730, 731, 740, 750, 751, 752, 753.
-
Review user role assignments for privilege escalationExecute transaction PFCG or use transaction SUIM (User Information System) to review role assignments. Look for users assigned to roles outside their normal scope, particularly roles with extensive authorization objects (e.g., SAP_ALL, SAP_NEW, or roles with S_DEVELOP, S_ADMI_FCD).Affected if Users possess roles or authorization objects they should not be entitled to access.
-
Examine security audit logs for unauthorized accessExecute transaction SM20 or use transaction SAAB to review the security audit log. Filter for events related to authorization checks (specifically events 45 and 46) and look for patterns indicating bypass of authorization controls.Affected if Audit logs show authorization bypass attempts or successful accesses to privileged functions by users lacking proper entitlements.
-
Inspect critical authorization objectsExecute transaction SU03 or SU21 to review critical authorization objects related to administrative functions. Check objects like S_ADMI_FCD (Administration Functions), S_DEVELOP (ABAP Workbench), and S_CTS_ADMI (Change and Transport System).Affected if Authorization objects are configured with overly broad values or missing checks.
The environment is affected if the installed SAP NetWeaver AS ABAP version is any of 700, 701, 702, 710, 711, 730, 731, 740, 750, 751, 752, or 753 AND there is evidence of unauthorized role assignments or privilege escalation in audit logs.
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 Note to implement proper authorization checks. Conduct a review of user role assignments and audit logs to confirm no unauthorized privilege escalation has occurred.
- Check the SAP One Support Launchpad (launchpad.support.sap.com) for the specific SAP Security Note related to CVE-2022-29611
- Apply the relevant SAP Security Note patch to the affected SAP NetWeaver AS ABAP system
- After applying the patch, verify that the authorization checks are now enforced for the affected functionality
- Test the patched system to confirm normal operation and that privilege escalation is no longer possible
- Consult the SAP Security Guide for the ABAP system to ensure no further authorization gaps exist
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29611 — 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-2022-29611 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