# CVE-2018-1801: XML external entity in App Connect

> Remote attackers can exploit XML External Entity injection in IBM integration products to consume memory resources, causing denial of service.

- **Severity:** Medium 5.3 (`CVSS:3.0/A:L/AC:L/AV:N/C:N/I:N/PR:N/S:U/UI:N/E:U/RC:C/RL:O`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6978-8w7h-mg7h

## What is CVE-2018-1801?

CVE-2018-1801 is a medium-severity vulnerability in IBM App Connect, published on 4 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM App Connect V11.0.0.0 through V11.0.0.1, IBM Integration Bus V10.0.0.0 through V10.0.0.13, IBM Integration Bus V9.0.0.0 through V9.0.0.10, and WebSphere Message Broker V8.0.0.0 through V8.0.0.9 is vulnerable to a XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to consume memory resources. IBM X-Force ID: 149639.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2018-1801?

It affects 3 products.


Products: Ibm App Connect, Ibm Integration Bus, Ibm Websphere Message Broker.

## How do I fix CVE-2018-1801?

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

## Is CVE-2018-1801 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1801 and fix it if it is affected.

What it is: CVE-2018-1801 is a medium-severity vulnerability in IBM App Connect, published on 4 Feb 2019. 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-2018-1801 in the wild and no public exploit code.

Affected product: IBM App Connect. 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-2018-1801/ (Markdown: https://insights.sbomify.com/CVE-2018-1801/index.md)
```

## Sources

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

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