CVE-2019-17352: Malicious File Upload
First published: Tue Oct 08 2019(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| JFinal | <4.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-17352?
CVE-2019-17352 is considered a moderate severity vulnerability due to its potential to allow unauthorized file uploads.
How do I fix CVE-2019-17352?
To fix CVE-2019-17352, update JFinal to version 4.4 or later, where the vulnerability has been addressed.
What can be exploited in CVE-2019-17352?
CVE-2019-17352 allows an attacker to bypass the isSafeFile() function, enabling the upload of any file type, including .jsp files.
What versions of JFinal are affected by CVE-2019-17352?
JFinal versions up to, but not including, version 4.4 are affected by CVE-2019-17352.
What are the consequences of exploiting CVE-2019-17352?
Exploitation of CVE-2019-17352 can lead to unauthorized file uploads, potentially resulting in arbitrary code execution.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/references
- agent/weakness
- agent/author
- agent/first-publish-date
- agent/description
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/jfinal
- canonical/jfinal