# CVE-2017-3189: File upload in Administration Panel

> Unauthenticated attackers can upload arbitrary files via the Push Publishing feature, potentially leading to remote code execution and privilege escalation.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/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:** 24 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9mqm-jfh7-77gm

## What is CVE-2017-3189?

CVE-2017-3189 is a high-severity vulnerability in Dotcms Dotcms, published on 24 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The dotCMS administration panel, versions 3.7.1 and earlier, "Push Publishing" feature in Enterprise Pro is vulnerable to arbitrary file upload. When "Bundle" tar.gz archives uploaded to the Push Publishing feature are decompressed, there are no checks on the types of files which the bundle contains. This vulnerability combined with the path traversal vulnerability (CVE-2017-3188) can lead to remote command execution with the permissions of the user running the dotCMS application. An unauthenticated remote attacker may perform actions with the dotCMS administrator panel with the same permissions of a victim user or execute arbitrary system commands with the permissions of the user running the dotCMS application.

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

## Which versions are affected by CVE-2017-3189?

It affects 1 product.


Products: Dotcms Dotcms.

## How do I fix CVE-2017-3189?

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

## Is CVE-2017-3189 being exploited?

There is no known exploitation of CVE-2017-3189 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-2020-6754](https://insights.sbomify.com/CVE-2020-6754/): Path traversal 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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3189 and fix it if it is affected.

What it is: CVE-2017-3189 is a high-severity vulnerability in Dotcms Dotcms, published on 24 Jul 2018. 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-2017-3189 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-2017-3189/ (Markdown: https://insights.sbomify.com/CVE-2017-3189/index.md)
```

## Sources

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

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