dbcve.org
S\/4hanaApplication · Sap

CVE-2022-31597

MEDIUM · 5.4 CVSS v3.1 Published 2022-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Within SAP S/4HANA - versions S4CORE 101, 102, 103, 104, 105, 106, SAPSCORE 127, the application business partner extension for Spain/Slovakia does not perform necessary authorization checks for a low privileged authenticated user over the network, resulting in escalation of privileges leading to low impact on confidentiality and integrity of the 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 · moderate confidence

SAP S/4HANA business partner extension for Spain/Slovakia (versions S4CORE 101-106, SAPSCORE 127) lacks proper authorization checks, allowing authenticated low-privileged users to perform actions beyond their intended permissions through the network interface.

MitigationApply SAP security patches for this vulnerability. In the interim, restrict network access to the business partner extension and review user role assignments to limit exposure to low-privileged accounts.

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
S\/4hanaApplication
Affected:= 101= 102= 103= 104= 105= 106
SapscoreApplication
Affected:= 127

CVSS 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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if business partner extension for Spain/Slovakia is installed
    Check installed SAP packages using transaction code SPAM or SAINT (Package Manager). Look for packages related to country-specific business partner extensions for Spain (ES) or Slovakia (SK).
    Affected if The extension is installed and active in the SAP system
  2. Check S4CORE version
    In SAP GUI, use transaction code SM37 to view system version, or execute ABAP report RS_COMPONENT_VERSION to list installed components. Look for component S4CORE with version numbers 101, 102, 103, 104, 105, or 106.
    Affected if S4CORE version is 101 through 106 inclusive
  3. Check SAPSCORE version
    Execute ABAP report RS_COMPONENT_VERSION or check via transaction SM37. Look for component SAPSCORE version 127.
    Affected if SAPSCORE version equals 127
  4. Verify user role assignments for low-privileged accounts
    Use transaction code PFCG to review role definitions. Check which roles are assigned to users with limited privileges, particularly those accessing business partner (BP) transaction codes like BP, FD01, FD02, FD03.
    Affected if Low-privileged users have roles that grant access to business partner functions through the network interface
  5. Check network exposure of business partner extension
    Review SAP Gateway and ICM (Internet Communication Manager) configuration using transaction SMICM. Verify which network services and ports are exposed for the business partner extension.
    Affected if The business partner extension is accessible over network interfaces without proper access controls

A user is affected if they have S4CORE versions 101-106 or SAPSCORE version 127 installed with the Spain/Slovakia business partner extension active, and low-privileged users can access it over the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SAP security patches for this vulnerability. In the interim, restrict network access to the business partner extension and review user role assignments to limit exposure to low-privileged accounts.

Fix this in S\/4hana Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31597 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-31597 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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