NetweaverApplication · Sap

CVE-2018-2462

HIGH · 8.8 CVSS v3.0 Published 2018-09-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
In certain cases, BEx Web Java Runtime Export Web Service in SAP NetWeaver BI 7.30, 7.31. 7.40, 7.41, 7.50, does not sufficiently validate an XML document accepted from an untrusted source.

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 XML External Entity (XXE) injection vulnerability in SAP NetWeaver BI's BEx Web Java Runtime Export Web Service. The service accepts XML documents from untrusted sources without proper validation, allowing attackers to inject malicious XML that can be used for server-side request forgery, denial of service, or unauthorized file access.

MitigationApply SAP Security Note 2563841 (or subsequent relevant patches) to implement proper XML parser configuration with disabled external entity processing and schema validation. If patching is not immediately possible, disable the affected BEx Web Java Runtime Export Web Service until the patch can be applied.

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:= 7.30= 7.31= 7.40= 7.41= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/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. Identify installed SAP NetWeaver version
    Use SAP transaction code SM51 to display the SAP System Version, or check the SAP LMC中央管理控制台 for the NetWeaver release version. Alternatively, review system documentation or contact SAP Basis team for version information.
    Affected if The installed version matches 7.30, 7.31, 7.40, 7.41, or 7.50 from the affected versions list.
  2. Verify BEx Web Java Runtime is deployed
    Check SAP NetWeaver Administrator (NWA) or use transaction code SICF to verify if the BEx Web Java Runtime service hierarchy is active in the SAP portal. Look for service path patterns related to BEx Web or Business Explorer.
    Affected if The BEx Web Java Runtime component is deployed and visible in the SAP system services.
  3. Confirm Export Web Service is active
    In SAP NWA under Services, locate the BEx Web Java Runtime Export Web Service. Use transaction code SICF and search for ExportService or related BEx export endpoints to verify the service is active.
    Affected if The Export Web Service endpoint is in active state and responds to HTTP/HTTPS requests.
  4. Assess network exposure of the service
    Review SAP Gateway and ICM (Internet Communication Manager) exposure settings. Check transaction code SMICM to determine if the service is bound to external-facing interfaces or accessible from untrusted networks.
    Affected if The service is bound to publicly accessible network interfaces without proper firewall or authentication restrictions.

A user is affected if they run SAP NetWeaver version 7.30-7.50 with the BEx Web Java Runtime Export Web Service enabled and exposed to untrusted sources, allowing external XML input without XXE protections 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SAP Security Note 2563841 (or subsequent relevant patches) to implement proper XML parser configuration with disabled external entity processing and schema validation. If patching is not immediately possible, disable the affected BEx Web Java Runtime Export Web Service until the patch can be applied.

Fix this in Netweaver Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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