Netweaver Application Server JavaApplication · Sap

CVE-2021-27598

MEDIUM · 5.3 CVSS v3.1 Published 2021-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 JAVA (Customer Usage Provisioning Servlet), versions - 7.31, 7.40, 7.50, allows an attacker to read some statistical data like product version, traffic, timestamp etc. because of missing authorization check in the servlet.

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

The Customer Usage Provisioning Servlet in SAP NetWeaver AS JAVA versions 7.31, 7.40, and 7.50 lacks proper authorization validation, allowing unauthenticated attackers to access statistical metadata including product version, traffic patterns, and timestamps.

MitigationApply the relevant SAP security patch (refer to SAP Security Note) to enforce authorization checks on the Customer Usage Provisioning Servlet and restrict access to statistical data.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 if SAP NetWeaver AS Java is running
    Check running Java processes or services for SAP NetWeaver components. Look for SAP J2EE engine processes or check system inventory for SAP Java applications.
    Affected if The system is running SAP NetWeaver Application Server Java
  2. Determine the installed SAP NetWeaver AS Java version
    Use SAP transaction code SM51 to view the SAP System Version, or check the SAR file manifest, or query the SAP kernel version via SAP kernel tools.
    Affected if The installed version matches 7.31, 7.40, or 7.50 exactly
  3. Locate the Customer Usage Provisioning Servlet
    Check the SAP J2EE engine configuration for servlet mappings. The servlet is typically deployed in the SAP J2EE Engine and may be accessible under paths containing 'UsageProvisioning' or 'Usage' in the URL structure.
    Affected if The Customer Usage Provisioning Servlet is deployed and accessible in the J2EE engine
  4. Test servlet accessibility without authentication
    Attempt to access the servlet URL directly without providing any SAP credentials. Use a web browser or HTTP tool to send an unauthenticated request to the servlet endpoint.
    Affected if The servlet responds with statistical metadata without requiring authentication
  5. Verify authorization configuration for the servlet
    Check the SAP J2EE security configuration (via Visual Administrator or deployment descriptors) to determine if proper authorization checks are enforced on the Customer Usage Provisioning Servlet.
    Affected if No authorization constraints are configured or the servlet is mapped to an unconstrained security role

A user is affected if their system runs SAP NetWeaver AS Java versions 7.31, 7.40, or 7.50 AND the Customer Usage Provisioning Servlet is accessible without authentication.

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 (refer to SAP Security Note) to enforce authorization checks on the Customer Usage Provisioning Servlet and restrict access to statistical data.

Fix this in Netweaver Application Server Java Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-27598 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-27598 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