dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2022-22540

HIGH · 7.5 CVSS v3.1 Published 2022-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
SAP NetWeaver AS ABAP (Workplace Server) - versions 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, 756, 787, allows an attacker to execute crafted database queries, that could expose the backend database. Successful attacks could result in disclosure of a table of contents from the system, but no risk of modification possible.

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

SQL injection vulnerability in SAP NetWeaver AS ABAP Workplace Server allows attackers to execute crafted database queries against the backend database. Successful exploitation reveals table of contents and other sensitive database information, but does not permit data modification.

MitigationApply SAP security notes/patches addressing CVE-2022-22540 to affected NetWeaver versions. Until patches are applied, restrict network access to the Workplace Server from untrusted sources.

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
Netweaver Application Server AbapApplication
Affected:= 700= 701= 702= 731= 740= 750= 751= 752= 753= 754= 755= 756

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 ABAP version
    Use transaction code SM51 in SAP GUI or execute the ABAP statement 'SYSTEM_FLUG' to retrieve the SAP NetWeaver version. Alternatively, check the SAP System Information via SAP Logon pad properties or use transaction code 'SLICENSE' to confirm the kernel and ABAP release version.
    Affected if The version matches one of the affected releases: 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, or 756.
  2. Verify Workplace Server component is installed
    Check if the SAP NetWeaver Application Server ABAP Workplace Server (sometimes labeled as 'SAP Enterprise Portal' or 'Web Container' component) is present. Use transaction code 'SPAM' or 'SAINT' to view installed software components, or check transaction code 'SM37' for running Workplace Server background jobs.
    Affected if The Workplace Server component is installed and active on the affected ABAP version.
  3. Confirm network exposure of Workplace Server
    Review SAP Gateway and ICM (Internet Communication Manager) configurations. Use transaction code 'SMICM' to check HTTP/HTTPS listeners. Verify whether the Workplace Server port (typically 50000 series or custom) is exposed to untrusted networks. Inspect firewall rules and SAP Profile parameters (icm/server_port_*) for external accessibility.
    Affected if The Workplace Server is reachable from untrusted network segments or the internet.
  4. Inspect logs for suspicious SQL patterns
    Examine SAP transaction code 'ST03N' for workload analysis, and review ABAP application logs via transaction 'SLG1' for object 'ABAP' with object variant 'SQL'. Check the SAP System Log (transaction 'SM37' or 'SLG1' with object 'SYSTEM') for unexpected SQL syntax or database table access patterns originating from the Workplace Server.
    Affected if Unusual or crafted SQL queries appear in application logs, particularly those accessing system tables like DD02L, DD03L, or other data dictionary objects.

A user is affected if they run SAP NetWeaver AS ABAP versions 700-756 with the Workplace Server component enabled and accessible, particularly if exposed to untrusted networks.

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 notes/patches addressing CVE-2022-22540 to affected NetWeaver versions. Until patches are applied, restrict network access to the Workplace Server from untrusted sources.

Fix this in Netweaver Application Server Abap Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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 locally
dbcve dependency scanner

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