# CVE-2020-10569: File upload in n/a

> Attackers can upload malicious files and execute commands via GhostCat chaining in SysAid On-Premise.

- **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:** 21 Apr 2020
- **Updated:** 18 Nov 2024
- **Also known as:** GHSA-66pv-97pv-f4qx

## What is CVE-2020-10569?

CVE-2020-10569 is a critical vulnerability in n/a, published on 21 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SysAid On-Premise 20.1.11, by default, allows the AJP protocol port, which is vulnerable to a GhostCat attack. Additionally, it allows unauthenticated access to upload files, which can be used to execute commands on the system by chaining it with a GhostCat attack. NOTE: This may be a duplicate of CVE-2020-1938

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Sysaid On-Premise.

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

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

## Is CVE-2020-10569 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10569 is a critical vulnerability in n/a, published on 21 Apr 2020. 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-2020-10569 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-10569/ (Markdown: https://insights.sbomify.com/CVE-2020-10569/index.md)
```

## Sources

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

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