# CVE-2020-6754: Path traversal in n/a

> Attackers can exploit directory traversal to read protected files or upload malicious JSP files, leading to remote code execution on the dotCMS server.

- **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:** 5 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qxjv-gj9g-c373

## What is CVE-2020-6754?

CVE-2020-6754 is a critical path traversal vulnerability in Dotcms Dotcms, published on 5 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

dotCMS before 5.2.4 is vulnerable to directory traversal, leading to incorrect access control. It allows an attacker to read or execute files under $TOMCAT_HOME/webapps/ROOT/assets (which should be a protected directory). Additionally, attackers can upload temporary files (e.g., .jsp files) into /webapps/ROOT/assets/tmp_upload, which can lead to remote command execution (with the permissions of the user running the dotCMS application).

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Dotcms Dotcms.

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

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

## Is CVE-2020-6754 being exploited?

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

## Other vulnerabilities in Dotcms Dotcms

- [CVE-2022-26352](https://insights.sbomify.com/CVE-2022-26352/): dotCMS Unrestricted Upload of File (critical 9.8, exploited in the wild)
- [CVE-2020-19138](https://insights.sbomify.com/CVE-2020-19138/): File upload in n/a (critical 9.8)
- [CVE-2017-5344](https://insights.sbomify.com/CVE-2017-5344/): SQL injection in n/a (critical 9.8)
- [CVE-2016-2355](https://insights.sbomify.com/CVE-2016-2355/): SQL injection in n/a (critical 9.8)
- [CVE-2016-8902](https://insights.sbomify.com/CVE-2016-8902/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-6754 is a critical path traversal vulnerability in Dotcms Dotcms, published on 5 Feb 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-6754 in the wild and no public exploit code.

Affected product: Dotcms Dotcms. 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-6754/ (Markdown: https://insights.sbomify.com/CVE-2020-6754/index.md)
```

## Sources

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

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