# CVE-2020-9361: Denial of service in n/a

> Local users with specific privileges can cause a denial of service in CryptoPro CSP on 64-bit platforms due to mishandled user-mode input.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3rrh-rx2j-x9xj

## What is CVE-2020-9361?

CVE-2020-9361 is a medium-severity denial of service vulnerability in n/a, published on 23 Oct 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CryptoPro CSP through 5.0.0.10004 on 64-bit platforms allows local users with the SeChangeNotifyPrivilege right to cause denial of service because user-mode input is mishandled during process creation.

## Which versions are affected by CVE-2020-9361?

It affects 1 product.


Products: Cryptopro Csp.

## How do I fix CVE-2020-9361?

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

## Is CVE-2020-9361 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-9331](https://insights.sbomify.com/CVE-2020-9331/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-9361 and fix it if it is affected.

What it is: CVE-2020-9361 is a medium-severity denial of service vulnerability in n/a, published on 23 Oct 2020. 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-2020-9361 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-2020-9361/ (Markdown: https://insights.sbomify.com/CVE-2020-9361/index.md)
```

## Sources

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

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