# CVE-2024-42374: XML injection in SAP BEx Web Java Runtime Export Web Service

> An attacker can exploit XML injection to retrieve sensitive information and cause denial of service in SAP BEx Web Java Runtime Export Web Service.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2024
- **Updated:** 14 Aug 2024
- **Also known as:** GHSA-r82q-4998-95r2

## What is CVE-2024-42374?

CVE-2024-42374 is a high-severity vulnerability in SAP_SE SAP BEx Web Java Runtime Export Web Service, published on 13 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-91 (XML Injection)

## Which versions are affected by CVE-2024-42374?

It affects 1 product.


Products: Sap Bex Web Java Runtime Export Web Service.

## How do I fix CVE-2024-42374?

No fix has been published for CVE-2024-42374 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-42374 being exploited?

There is no known exploitation of CVE-2024-42374 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42374 and fix it if it is affected.

What it is: CVE-2024-42374 is a high-severity vulnerability in SAP_SE SAP BEx Web Java Runtime Export Web Service, published on 13 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-42374 in the wild and no public exploit code.

Affected product: SAP_SE SAP BEx Web Java Runtime Export Web Service. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-42374/ (Markdown: https://insights.sbomify.com/CVE-2024-42374/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-42374
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-42374
- OSV: https://osv.dev/vulnerability/CVE-2024-42374

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-42374/
Summaries are generated and may contain mistakes; the official description above is the record.