dbcve.org
Netweaver Java Web ApplicationApplication · Sap

CVE-2018-2371

MEDIUM · 6.1 CVSS v3.0 Published 2018-02-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
The SAML 2.0 service provider of SAP Netweaver AS Java Web Application, 7.50, does not sufficiently encode user controlled inputs, which results in Cross-Site Scripting (XSS) vulnerability.

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

Cross-Site Scripting (XSS) vulnerability in SAP Netweaver AS Java 7.50's SAML 2.0 service provider due to insufficient encoding of user-controlled inputs. An attacker could inject malicious scripts through SAML parameters that are reflected back to users.

MitigationImplement proper output encoding for all user-controlled SAML parameters before rendering. Validate and sanitize inputs at the application layer, and apply context-specific encoding based on where the data is displayed (HTML, JavaScript, URL).

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 Java Web ApplicationApplication
Affected:= 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/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. Verify SAP NetWeaver AS Java version
    Access the SAP NetWeaver Administrator (NWA) or use the SAP LMND command to retrieve the installed Java version. Navigate to System -> Overview in NWA, or run 'sapcontrol -nr <instance> -function GetVersionInfo' to confirm the exact version number.
    Affected if The installed version is exactly 7.50 (exact match to the affected version)
  2. Confirm SAML 2.0 service provider is enabled
    In SAP NetWeaver Administrator, navigate to Configuration -> Security -> SAML 2.0 -> Service Provider. Alternatively, check the SAML configuration file in the deployment directory (typically under /usr/sap/<SID>/<instance>/j2ee/cluster/global/security/saml or via the SAP Management Console). Verify if the SAML 2.0 local service provider is configured and active.
    Affected if SAML 2.0 service provider is configured and enabled in the SAP NetWeaver Java system
  3. Inspect SAML metadata and parameter handling
    Export the SAML 2.0 service provider metadata via the NWA SAML configuration page or by accessing the metadata endpoint (typically /saml/metadata). Review the configuration for how SAML assertion attributes and parameters are processed and whether user-controlled values from SAML responses are reflected in any web interfaces.
    Affected if The SAML configuration accepts and reflects user-supplied values in SAML parameters without proper encoding
  4. Check for SAML-related error messages or logs
    Review SAP NetWeaver Java logs (default location: /usr/sap/<SID>/<instance>/j2ee/cluster/<node>/log) for SAML-related error entries or debugging output that may contain unsanitized user input. Use transaction code SLG1 or the Log Viewer in NWA to search for SAML and XSS patterns.
    Affected if Logs contain SAML parameters or assertion data being logged or displayed without encoding

A user is affected if they are running SAP NetWeaver AS Java version 7.50 and have the SAML 2.0 service provider enabled, as the XSS vulnerability exists in how SAML parameters are processed and reflected.

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

Implement proper output encoding for all user-controlled SAML parameters before rendering. Validate and sanitize inputs at the application layer, and apply context-specific encoding based on where the data is displayed (HTML, JavaScript, URL).

Fix this in Netweaver Java Web Application Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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