dbcve.org
Bex Web Java Runtime Export Web ServiceApplication · Sap

CVE-2024-42374

HIGH · 8.2 CVSS v3.1 Published 2024-08-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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
BEx Web Java Runtime Export Web Service does not sufficiently validate an XML document accepted from an untrusted source. An attacker can retrieve information from the SAP ADS system and exhaust the number of XMLForm service which makes the SAP ADS rendering (PDF creation) unavailable. This affects the confidentiality and availability of the application.

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

XML validation vulnerability in BEx Web Java Runtime Export Web Service allows untrusted XML documents to be processed without sufficient validation. Attackers can exploit this to retrieve sensitive information from SAP ADS system and exhaust XMLForm services, causing PDF rendering (ADS) to become unavailable.

MitigationApply SAP security notes/patches for this vulnerability and implement proper XML input validation/disable external entity processing at the application or XML parser level.

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
Bex Web Java Runtime Export Web ServiceApplication
Affected:= bi-base-b_7.5= bi-base-e_7.5= bi-base-s_7.5= bi-ibc_7.5= biwebapp_7.5

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
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 BEx Web Java components
    Locate and inspect the SAP BEx Web application components. Check for directories or deployment files containing 'bi-base-b', 'bi-base-e', 'bi-base-s', 'bi-ibc', or 'biwebapp' with version 7.5. Use SAP SAPMMC or system management tools to list installed SAP BusinessObjects components.
    Affected if Any of the listed components (bi-base-b_7.5, bi-base-e_7.5, bi-base-s_7.5, bi-ibc_7.5, biwebapp_7.5) are installed and running.
  2. Verify BEx Web Java Runtime Export Web Service is enabled
    Check the SAP system configuration for the BEx Web Java Runtime Export Web Service. This is typically found in the SAP NetWeaver Administrator or SAP Management Console under web service configurations for the BEx system. Look for Export Web Service endpoints that handle XML document processing.
    Affected if The Export Web Service endpoint is exposed and accessible for XML document submissions.
  3. Check XML processing configuration
    Inspect the configuration files for the BEx Web Java Runtime Export Web Service. Look for XML parser settings, particularly whether XML schema validation is enabled or disabled. Check for any custom XML handler configurations that may indicate relaxed validation.
    Affected if XML schema validation is disabled, not configured, or set to permissive mode for incoming documents.
  4. Verify connectivity to Adobe Document Services (ADS)
    Review logs or network configuration to confirm the BEx Web service can communicate with the SAP Adobe Document Services system. Check if ADS is deployed in the landscape, as the vulnerability allows the BEx service to make requests to ADS.
    Affected if ADS is accessible from the BEx Web Java Runtime environment and the service has network access to ADS endpoints.

Your environment is affected if any of the listed BEx Web Java components (version 7.5) are installed with the Export Web Service enabled and accessible, particularly if XML validation is not strictly configured.

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 for this vulnerability and implement proper XML input validation/disable external entity processing at the application or XML parser level.

Fix this in Bex Web Java Runtime Export Web Service Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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