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

> Attackers can execute arbitrary C# code on machines rendering reports when Compilation Mode is enabled in Stimulsoft Reports.

- **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:** 29 Oct 2022
- **Updated:** 7 May 2025
- **Also known as:** GHSA-gg9g-9v4f-9pj3

## What is CVE-2021-42777?

CVE-2021-42777 is a critical code injection vulnerability in n/a, published on 29 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stimulsoft (aka Stimulsoft Reports) 2013.1.1600.0, when Compilation Mode is used, allows an attacker to execute arbitrary C# code on any machine that renders a report, including the application server or a user's local machine, as demonstrated by System.Diagnostics.Process.Start.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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

It affects 1 product.


Products: Stimulsoft Reports.

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

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

## Is CVE-2021-42777 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15865](https://insights.sbomify.com/CVE-2020-15865/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-42777 is a critical code injection vulnerability in n/a, published on 29 Oct 2022. 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-42777 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-42777/ (Markdown: https://insights.sbomify.com/CVE-2021-42777/index.md)
```

## Sources

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

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