# CVE-2019-17352: JFinal file validation vulnerability

> Attackers can bypass file type restrictions to upload malicious files, potentially leading to remote code execution in applications using the JFinal cos library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-279p-pc38-xx4p

## What is CVE-2019-17352?

CVE-2019-17352 is a high-severity vulnerability in n/a, published on 8 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In JFinal cos before 2019-08-13, as used in JFinal 4.4, there is a vulnerability that can bypass the isSafeFile() function: one can upload any type of file. For example, a .jsp file may be stored and almost immediately deleted, but this deletion step does not occur for certain exceptions.

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

## Which versions are affected by CVE-2019-17352?

2 open source packages ship an affected version, including com.jfinal:jfinal. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.jfinal:jfinal` | Maven | All versions | 4.5 |
| `com.jfinal:jfinal` | Maven | All versions | 4.5 |

Products: Jfinal Jfinal.

## How do I fix CVE-2019-17352?

Upgrade com.jfinal:jfinal to 4.5 or later.

## Is CVE-2019-17352 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-31635](https://insights.sbomify.com/CVE-2021-31635/): jFinal Server-Side Template Injection vulnerability (critical 9.8)
- [CVE-2021-31649](https://insights.sbomify.com/CVE-2021-31649/): JFinal Java Deserialization Vulnerability (critical 9.8)
- [CVE-2021-33348](https://insights.sbomify.com/CVE-2021-33348/): Cross-site scripting in jfinal (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-17352 and fix it if it is affected.

What it is: CVE-2019-17352 is a high-severity vulnerability in n/a, published on 8 Oct 2019. 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-2019-17352 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.jfinal:jfinal (Maven): affected all versions; fixed in 4.5
- com.jfinal:jfinal (Maven): affected all versions; fixed in 4.5

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

## Sources

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

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