# CVE-2021-44042: Cross-site scripting in n/a

> Attackers can inject JavaScript into UiPath Assistant via URI handler arguments, leading to code execution within the Electron application context.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 14 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vvrp-5qgw-cc82

## What is CVE-2021-44042?

CVE-2021-44042 is a critical cross-site scripting vulnerability in n/a, published on 14 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in UiPath Assistant 21.4.4. User-controlled data supplied to the --process-start argument of the URI handler for uipath-assistant:// is not correctly encoded, resulting in attacker-controlled content being injected into the error message displayed (when the injected content does not match an existing process). A determined attacker could leverage this to execute JavaScript in the context of the Electron application.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

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

It affects 1 product.


Products: Uipath Assistant.

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

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

## Is CVE-2021-44042 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-44041](https://insights.sbomify.com/CVE-2021-44041/): Path traversal in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-44042 is a critical cross-site scripting vulnerability in n/a, published on 14 Dec 2021. 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-2021-44042 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-2021-44042/ (Markdown: https://insights.sbomify.com/CVE-2021-44042/index.md)
```

## Sources

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

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