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

> Unauthenticated attackers can upload arbitrary files to execute commands with root privileges or access database data.

- **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:** 18 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qgmc-9h97-pfv6

## What is CVE-2020-9423?

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

### Official description

LogicalDoc before 8.3.3 could allow an attacker to upload arbitrary files, leading to command execution or retrieval of data from the database. LogicalDoc provides a functionality to add documents. Those documents could then be used for multiple tasks, such as version control, shared among users, applying tags, etc. This functionality could be abused by an unauthenticated attacker to upload an arbitrary file in a restricted folder. This would lead to the executions of malicious commands with root privileges.

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

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

It affects 1 product.


Products: Logicaldoc Logicaldoc.

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

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

## Is CVE-2020-9423 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-13542](https://insights.sbomify.com/CVE-2020-13542/): Privilege escalation in LogicalDoc (critical 9.3)
- [CVE-2017-1000021](https://insights.sbomify.com/CVE-2017-1000021/): XML external entity in n/a (high 8.8)
- [CVE-2017-1000022](https://insights.sbomify.com/CVE-2017-1000022/): Privilege escalation in n/a (high 8.8)
- [CVE-2024-54449](https://insights.sbomify.com/CVE-2024-54449/): Remote Code Execution (RCE) via Arbitrary File Write In Document API (high 8.7)
- [CVE-2024-54448](https://insights.sbomify.com/CVE-2024-54448/): Remote Code Execution (RCE) via Automation Scripting (high 8.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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