dbcve.org
NetweaverApplication · Sap

CVE-2023-36922

HIGH · 8.8 CVSS v3.1 Published 2023-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
Due to programming error in function module and report, IS-OIL component in SAP ECC and SAP S/4HANA allows an authenticated attacker to inject an arbitrary operating system command into an unprotected parameter in a common (default) extension.  On successful exploitation, the attacker can read or modify the system data as well as shut down 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 · high confidence

This is an OS command injection vulnerability in SAP IS-OIL component affecting SAP ECC and SAP S/4HANA. Due to a programming error in a function module and report, an authenticated attacker can inject arbitrary operating system commands through an unprotected parameter in a common (default) extension, potentially allowing full system compromise including reading/modifying data or shutting down the system.

MitigationApply the relevant SAP security patch (security note) for CVE-2023-36922 to the IS-OIL component in affected SAP ECC and S/4HANA systems. As a compensating control, review and restrict access to the vulnerable function module and implement input validation on the affected parameter.

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
NetweaverApplication
Affected:= 600= 602= 603= 604= 605= 606= 617= 618= 800= 802= 803= 804

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
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 checks

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

  1. Check SAP NetWeaver version
    Execute transaction SM51 or use SAPMMC to view the SAP NetWeaver Application Server release version. Alternatively, use transaction SXMB_MONI or check the system information in SAP Logon. Compare the version number against the affected versions: 600, 602, 603, 604, 605, 606, 617, 618, 800, 802, 803, 804.
    Affected if The installed NetWeaver version matches any of the listed affected version numbers.
  2. Verify IS-OIL component is installed
    Use transaction SE16 to query table CVERS_COMPONENTS or use transaction SPAM to check installed software components. Look for component IS-OIL or related Oil & Gas industry components in the installed component list.
    Affected if The IS-OIL component (Oil & Gas) is present in the SAP system.
  3. Identify vulnerable function module access
    Use transaction SE37 (Function Builder) or SE84 to search for function modules within the IS-OIL component that handle external command execution or system calls. Review the authorization landscape using transaction SU53 after attempting to access suspected modules.
    Affected if An authenticated user has access to function modules in IS-OIL that accept external parameters for OS command execution.
  4. Check common extension configuration
    Use transaction SPRO to access the SAP Reference IMG and navigate to IS-OIL related configuration nodes. Check the extension settings under the common (default) extension framework to identify if the vulnerable parameter interface is exposed.
    Affected if The common extension for IS-OIL is enabled and accessible to authenticated users without additional security restrictions.

A system is affected if it runs a vulnerable SAP NetWeaver version (600, 602, 603, 604, 605, 606, 617, 618, 800, 802, 803, or 804) with the IS-OIL component installed and the unprotected parameter in the common extension accessible to authenticated users.

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 the relevant SAP security patch (security note) for CVE-2023-36922 to the IS-OIL component in affected SAP ECC and S/4HANA systems. As a compensating control, review and restrict access to the vulnerable function module and implement input validation on the affected parameter.

Fix this in Netweaver Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-36922 — 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-2023-36922 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