# CVE-2021-45785: Cross-site request forgery in n/a

> An attacker can force a server restart via CSRF, causing denial of service, if a privileged user visits a malicious page.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Jun 2024
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w65f-4h2f-cpj2

## What is CVE-2021-45785?

CVE-2021-45785 is a medium-severity vulnerability in n/a, published on 24 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

TruDesk Help Desk/Ticketing Solution v1.1.11 is vulnerable to a Cross-Site Request Forgery (CSRF) attack which would allow an attacker to restart the server, causing a DoS attack. The attacker must craft a webpage that would perform a GET request to the /api/v1/admin/restart endpoint, then the victim (who has sufficient privileges), would visit the page and the server restart would begin. The attacker must know the full URL that TruDesk is on in order to craft the webpage.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Trudesk Project Trudesk.

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

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

## Is CVE-2021-45785 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-45785 exists.

## Other vulnerabilities in n/a

- [CVE-2022-2023](https://insights.sbomify.com/CVE-2022-2023/): Incorrect Use of Privileged APIs in polonel/trudesk (critical 10.0)
- [CVE-2022-1770](https://insights.sbomify.com/CVE-2022-1770/): Improper Privilege Management in polonel/trudesk (critical 9.9)
- [CVE-2022-2128](https://insights.sbomify.com/CVE-2022-2128/): Unrestricted Upload of File with Dangerous Type in polonel/trudesk (critical 9.6)
- [CVE-2022-1931](https://insights.sbomify.com/CVE-2022-1931/): Incorrect Synchronization in polonel/trudesk (critical 9.1)
- [CVE-2022-1947](https://insights.sbomify.com/CVE-2022-1947/): Use of Incorrect Operator in polonel/trudesk (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-45785 is a medium-severity vulnerability in n/a, published on 24 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-45785 exists.

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-45785/ (Markdown: https://insights.sbomify.com/CVE-2021-45785/index.md)
```

## Sources

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

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