CVE-2022-41264
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 · uneditedDue to the unrestricted scope of the RFC function module, SAP BASIS - versions 731, 740, 750, 751, 752, 753, 754, 755, 756, 757, 789, 790, 791, allows an authenticated non-administrator attacker to access a system class and execute any of its public methods with parameters provided by the attacker. On successful exploitation the attacker can have full control of the system to which the class belongs, causing a high impact on the integrity of the application.
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 confidenceThis is an authorization bypass vulnerability in SAP BASIS where the RFC (Remote Function Call) function module has unrestricted scope. An authenticated non-administrator attacker can access system classes and execute their public methods with attacker-controlled parameters, achieving arbitrary code execution with system-level privileges.
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.31= 7.40= 7.50= 7.51= 7.52= 7.53= 7.54= 7.55= 7.56= 7.57= 7.89= 7.90CVSS 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 installed SAP BASIS versionLog into SAP system and execute transaction SM51 (System Information) or use command sapcontrol -nr <instance> -function GetVersionInfo to retrieve the BASIS version. Alternatively, check transaction SAIS for kernel release information.Affected if The installed BASIS version matches one of the affected versions: 7.31, 7.40, 7.50, 7.51, 7.52, 7.53, 7.54, 7.55, 7.56, 7.57, 7.89, or 7.90.
-
Verify RFC function module exposureUse transaction SM59 (RFC Destinations) to view configured RFC connections. Examine whether function modules with system-level access are exposed. Check transaction SE37 (Function Builder) for function modules that provide access to system classes.Affected if RFC function modules that allow access to system classes and their public methods are accessible without proper scope restrictions.
-
Check authorization for RFC function module accessUse transaction SUIM (User Information System) or check user role assignments via PFCG. Examine whether non-administrator users have roles that grant access to the unrestricted RFC function module. Review authorization object S_RFC and check for unchecked scope values.Affected if Non-administrator users possess roles or authorizations that allow them to call RFC function modules with unrestricted scope, bypassing authorization checks.
-
Inspect RFC scope configurationReview the configuration of the specific RFC function module in transaction SE37 or SM59. Look for scope parameters or authorization settings that should enforce role-based access but are instead set to allow unrestricted access.Affected if The RFC function module scope parameter is set to a value that bypasses or does not enforce proper authorization validation for non-administrator users.
A user is affected if their SAP BASIS version matches the affected list AND the RFC function module with unrestricted scope is accessible to authenticated non-administrator users without proper authorization checks.
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/patch for CVE-2022-41264 and restrict the RFC function module scope to enforce proper authorization checks for non-administrator users.
SAP BASIS 7.90 or higher (specific version depends on your SAP ERP release; for SAP ERP 7.0 -> 7.90, for SAP S/4HANA -> appropriate S/4HANA version)
- 1. Identify the current SAP BASIS version by checking system information in SAP transaction SM51
- 2. Review the SAP Security Note for CVE-2022-41264 in the SAP Support Portal (search by CVE ID or note number)
- 3. Download and apply the relevant SAP Security Note patch for your BASIS version
- 4. If a patch is not available for your version, plan an upgrade to the next supported BASIS version (7.90 or higher)
- 5. After applying the patch or upgrade, verify the RFC function module restrictions are in place
- 6. Test critical RFC-enabled function modules to confirm proper access controls are enforced
- 7. Review user roles and remove unnecessary RFC access for non-administrator users
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41264 — 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-41264 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