# CVE-2018-15506: XML external entity in n/a

> Remote attackers can exploit an XXE vulnerability in BubbleUPnP to read arbitrary files or achieve remote code execution via SMB relay attacks.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 19 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rhh7-fxcj-gr67

## What is CVE-2018-15506?

CVE-2018-15506 is a critical vulnerability in n/a, published on 19 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In BubbleUPnP 0.9 update 30, the XML parsing engine for SSDP/UPnP functionality is vulnerable to an XML External Entity Processing (XXE) attack. Remote, unauthenticated attackers can use this vulnerability to: (1) Access arbitrary files from the filesystem with the same permission as the user account running BubbleUPnP, (2) Initiate SMB connections to capture a NetNTLM challenge/response and crack the cleartext password, or (3) Initiate SMB connections to relay a NetNTLM challenge/response and achieve Remote Command Execution in Windows domains.

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

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

It affects 1 product.


Products: Bubblesoftapps Bubbleupnp.

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

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

## Is CVE-2018-15506 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-15506 is a critical vulnerability in n/a, published on 19 Jun 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-15506 in the wild and no public exploit code.

Affected product: n/a. 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-15506/ (Markdown: https://insights.sbomify.com/CVE-2018-15506/index.md)
```

## Sources

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

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