# CVE-2021-21957: Command injection in Dream Report

> Attackers can achieve privilege escalation and code execution in Dream Report ODS Remote Connector by providing a malicious file to trigger command injection.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 8 Dec 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-vjjq-q5v7-9wmx

## What is CVE-2021-21957?

CVE-2021-21957 is a high-severity command injection vulnerability in Dream Report, published on 8 Dec 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A privilege escalation vulnerability exists in the Remote Server functionality of Dream Report ODS Remote Connector 20.2.16900.0. A specially-crafted command injection can lead to elevated capabilities. An attacker can provide a malicious file to trigger this vulnerability.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Dreamreport Remote Connector.

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

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

## Is CVE-2021-21957 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-21957 is a high-severity command injection vulnerability in Dream Report, published on 8 Dec 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-21957 in the wild and no public exploit code.

Affected product: Dream Report. 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-21957/ (Markdown: https://insights.sbomify.com/CVE-2021-21957/index.md)
```

## Sources

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

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