# CVE-2019-11216: XML external entity in n/a

> Authenticated attackers can exploit XML External Entity vulnerabilities in BMC Smart Reporting to read local files or cause denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pf85-6vfc-9453

## What is CVE-2019-11216?

CVE-2019-11216 is a medium-severity vulnerability in n/a, published on 4 Dec 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

BMC Smart Reporting 7.3 20180418 allows authenticated XXE within the import functionality. One can import a malicious XML file and perform XXE attacks to download local files from the server, or do DoS attacks with XML expansion attacks. XXE with direct response and XXE OOB are allowed.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference), CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2019-11216?

It affects 1 product.


Products: Bmc Remedy Smart Reporting.

## How do I fix CVE-2019-11216?

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

## Is CVE-2019-11216 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-1010147](https://insights.sbomify.com/CVE-2019-1010147/): Cross-site scripting in Smart Reporting (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11216 and fix it if it is affected.

What it is: CVE-2019-11216 is a medium-severity vulnerability in n/a, published on 4 Dec 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-11216 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-2019-11216/ (Markdown: https://insights.sbomify.com/CVE-2019-11216/index.md)
```

## Sources

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

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