# CVE-2021-28822: TIBCO Enterprise Message Service Windows Platform Artifact Search vulnerability

> A local attacker can exploit an artifact search vulnerability to execute malicious code with elevated privileges on TIBCO EMS Windows components.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Mar 2021
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-xpvq-rpfc-g9rw

## What is CVE-2021-28822?

CVE-2021-28822 is a high-severity vulnerability in TIBCO Enterprise Message Service, published on 23 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Enterprise Message Service Server (tibemsd), Enterprise Message Service Central Administration (tibemsca), Enterprise Message Service JSON configuration generator (tibemsconf2json), and Enterprise Message Service C API components of TIBCO Software Inc.'s TIBCO Enterprise Message Service, TIBCO Enterprise Message Service - Community Edition, and TIBCO Enterprise Message Service - Developer Edition contain a vulnerability that theoretically allows a low privileged attacker with local access on the Windows operating system to insert malicious software. The affected component can be abused to execute the malicious software inserted by the attacker with the elevated privileges of the component. This vulnerability results from the affected component searching for run-time artifacts outside of the installation hierarchy. Affected releases are TIBCO Software Inc.'s TIBCO Enterprise Message Service: versions 8.5.1 and below, TIBCO Enterprise Message Service - Community Edition: versions 8.5.1 and below, and TIBCO Enterprise Message Service - Developer Edition: versions 8.5.1 and below.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2021-28822?

It affects 1 product.


Products: Tibco Enterprise Message Service.

## How do I fix CVE-2021-28822?

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

## Is CVE-2021-28822 being exploited?

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

## Other vulnerabilities in TIBCO Enterprise Message Service

- [CVE-2009-1291](https://insights.sbomify.com/CVE-2009-1291/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-1704](https://insights.sbomify.com/CVE-2008-1704/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-5655](https://insights.sbomify.com/CVE-2007-5655/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-5656](https://insights.sbomify.com/CVE-2007-5656/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-5657](https://insights.sbomify.com/CVE-2007-5657/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-28822 and fix it if it is affected.

What it is: CVE-2021-28822 is a high-severity vulnerability in TIBCO Enterprise Message Service, published on 23 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-28822 in the wild and no public exploit code.

Affected product: TIBCO Enterprise Message 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-2021-28822/ (Markdown: https://insights.sbomify.com/CVE-2021-28822/index.md)
```

## Sources

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

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