# CVE-2019-8999: XML external entity in BlackBerry UEM

> An XML External Entity vulnerability in BlackBerry UEM allows attackers to read files on systems reachable by the service account.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qxhf-xwcg-8fxp

## What is CVE-2019-8999?

CVE-2019-8999 is a high-severity vulnerability in BlackBerry UEM, published on 18 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An XML External Entity vulnerability in the UEM Core of BlackBerry UEM version(s) earlier than 12.10.1a could allow an attacker to potentially gain read access to files on any system reachable by the UEM service account.

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

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

It affects 1 product.


Products: Blackberry Unified Endpoint Management.

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

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

## Is CVE-2019-8999 being exploited?

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

## Other vulnerabilities in BlackBerry UEM

- [CVE-2021-22153](https://insights.sbomify.com/CVE-2021-22153/): Code injection in n/a (high 7.3)
- [CVE-2021-22152](https://insights.sbomify.com/CVE-2021-22152/): Denial of service in n/a (medium 5.5)
- [CVE-2021-22154](https://insights.sbomify.com/CVE-2021-22154/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-8999 is a high-severity vulnerability in BlackBerry UEM, published on 18 Apr 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-2019-8999 in the wild and no public exploit code.

Affected product: BlackBerry UEM. 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-8999/ (Markdown: https://insights.sbomify.com/CVE-2019-8999/index.md)
```

## Sources

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

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