{"answers":{"affected":"2 open source packages ship an affected version, including com.jfinal:jfinal. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17352 in the wild and no public exploit code.","fix":"Upgrade com.jfinal:jfinal to 4.5 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2019-17352 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2019-17352 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.jfinal:jfinal (Maven): affected all versions; fixed in 4.5\n- com.jfinal:jfinal (Maven): affected all versions; fixed in 4.5\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-17352/ (Markdown: https://insights.sbomify.com/CVE-2019-17352/index.md)","id":"CVE-2019-17352","markdown":"https://insights.sbomify.com/CVE-2019-17352/index.md","name":"CVE-2019-17352","record":{"aliases":["GHSA-279p-pc38-xx4p"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JFinal cos library","requires_auth":"none","summary":"Attackers can bypass file type restrictions to upload malicious files, potentially leading to remote code execution in applications using the JFinal cos library.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jfinal","vendor":"jfinal"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"JFinal file validation vulnerability","id":"CVE-2019-17352","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"file_upload","year":"2019"},"n_packages":2,"n_references":3,"next":{"headline":"Missing authorization in n/a","id":"CVE-2019-17353"},"packages":[{"ecosystem":"Maven","fixed":["4.5"],"introduced":["0"],"last_affected":[],"package":"com.jfinal:jfinal","purl":null,"source":"GHSA-279p-pc38-xx4p"},{"ecosystem":"Maven","fixed":["4.5"],"introduced":["0"],"last_affected":[],"package":"com.jfinal:jfinal","purl":"pkg:maven/com.jfinal/jfinal","source":"GHSA-279p-pc38-xx4p"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2019-17351"},"products":["n/a"],"published":"2019-10-08","related":[{"cvss_score":9.8,"headline":"jFinal Server-Side Template Injection vulnerability","id":"CVE-2021-31635","kev_date_added":null,"published":"2023-06-26"},{"cvss_score":9.8,"headline":"JFinal Java Deserialization Vulnerability","id":"CVE-2021-31649","kev_date_added":null,"published":"2021-06-24"},{"cvss_score":6.1,"headline":"Cross-site scripting in jfinal","id":"CVE-2021-33348","kev_date_added":null,"published":"2021-06-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can bypass file type restrictions to upload malicious files, potentially leading to remote code execution in applications using the JFinal cos library.","url":"https://insights.sbomify.com/CVE-2019-17352/"}