# CVE-2021-35482: Code injection in n/a

> An attacker on the local network can achieve remote code execution with user privileges on devices connecting to the presentation system.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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:** 21 Jul 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-253w-3f25-wwwm

## What is CVE-2021-35482?

CVE-2021-35482 is a high-severity code injection vulnerability in n/a, published on 21 Jul 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Barco MirrorOp Windows Sender before 2.5.4.70. An attacker in the local network is able to achieve Remote Code Execution (with user privileges of the local user) on any device that tries to connect to a WePresent presentation system.

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

It affects 1 product.


Products: Barco Mirrorop Windows Sender.

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

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

## Is CVE-2021-35482 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-38142](https://insights.sbomify.com/CVE-2021-38142/): Security feature bypass in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-35482 is a high-severity code injection vulnerability in n/a, published on 21 Jul 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-35482 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-35482/ (Markdown: https://insights.sbomify.com/CVE-2021-35482/index.md)
```

## Sources

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

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