dbcve.org
Netweaver Application Server JavaApplication · Sap

CVE-2021-37535

CRITICAL · 9.8 CVSS v3.1 Published 2021-09-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Application Server Java (JMS Connector Service) - versions 7.11, 7.20, 7.30, 7.31, 7.40, 7.50, does not perform necessary authorization checks for user 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 confidence

The JMS Connector Service in SAP NetWeaver AS Java versions 7.11 through 7.50 lacks proper authorization checks, allowing unauthenticated or low-privilege users to perform operations on the Java Message Service that they should not have access to. This missing access control could enable unauthorized message reading, modification, or administrative operations on the JMS infrastructure.

MitigationApply the relevant SAP security patch for this vulnerability. In the interim, restrict network access to the JMS Connector Service to trusted IPs only and audit user role assignments to ensure least-privilege principles are followed.

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 JavaApplication
Affected:= 7.11= 7.20= 7.30= 7.31= 7.40= 7.50

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify SAP NetWeaver AS Java version
    Check the SAP system for the installed AS Java version using SAP transaction SM51 or by inspecting the SAP profile parameters. The version can also be found in the SAP Java engine startup logs or via the SAP Management Console.
    Affected if The installed version matches 7.11, 7.20, 7.30, 7.31, 7.40, or 7.50
  2. Verify JMS Connector Service is running
    Check if the JMS Connector Service is deployed and active in the SAP NetWeaver AS Java system. This can be verified through the SAP Visual Administrator (for older versions) or via the SAP NetWeaver Administrator (NWA) console under the Java System properties.
    Affected if The JMS Connector Service is enabled and running on the system
  3. Confirm JMS Connector is network-accessible
    Review the network binding configuration for the JMS Connector Service to determine if it is exposed to untrusted networks. Check the SAP Java Connector configuration files and HTTP service bindings.
    Affected if The JMS Connector Service is accessible from untrusted network segments or external IP addresses
  4. Audit JMS access control configuration
    Examine the authorization configuration for the JMS Connector Service to determine if proper role-based access controls are enforced. Review the assigned JMS-related roles and permissions in the SAP User Management engine.
    Affected if Low-privilege or unauthenticated users have been granted permissions to perform JMS operations beyond their intended access level

A system is affected if it runs SAP NetWeaver AS Java version 7.11 through 7.50 with the JMS Connector Service enabled and exposed without proper role-based authorization controls in place.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant SAP security patch for this vulnerability. In the interim, restrict network access to the JMS Connector Service to trusted IPs only and audit user role assignments to ensure least-privilege principles are followed.

Recommended fix Moderate confidence

SAP NetWeaver AS Java 7.50 or latest supported EHP release (EHP8 for SAP NetWeaver 7.5)

  1. 1. Identify the exact SAP NetWeaver Application Server Java version currently running using SAP LMDB or SAP NetWeaver Administrator
  2. 2. Review SAP Note 3078684 (or most recent relevant security note) for CVE-2021-37535 on the SAP Support Portal
  3. 3. Apply the latest available SAP Security Patch for NetWeaver AS Java that addresses missing authorization in the JMS Connector Service
  4. 4. After applying the patch, verify that authorization checks are now enforced for the JMS Connector Service
  5. 5. Test critical JMS operations (send, receive, create connections) with unprivileged users to confirm authorization is properly enforced
  6. 6. Restart the Java instance as required by the patch instructions
Caveat Review SAP Quick Sizer and SAP Note for any required configuration changes after patch; test JMS functionality in non-production first as patch may affect existing JMS connector configurations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Netweaver Application Server Java 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-2021-37535 — 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-2021-37535 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