# CVE-2022-45802: Apache StreamPark (incubating): Upload any file to any directory > Attackers can upload arbitrary files to any directory due to missing file type validation, potentially leading to code execution. - **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:** Yes - **Published:** 1 May 2023 - **Updated:** 21 Oct 2024 - **Also known as:** GHSA-6874-289g-f7h7 ## What is CVE-2022-45802? CVE-2022-45802 is a critical vulnerability in Apache StreamPark (incubating), published on 1 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Streampark allows any users to upload a jar as application, but there is no mandatory verification of the uploaded file type, causing users to upload some high-risk files, and may upload them to any directory, Users of the affected versions should upgrade to Apache StreamPark 2.0.0 or later Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type) ## Which versions are affected by CVE-2022-45802? 4 open source packages ship an affected version, including org.apache.streampark:streampark-common_2.11 and org.apache.streampark:streampark-common_2.12. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.streampark:streampark-common_2.11` | Maven | All versions | 2.0.0 | | `org.apache.streampark:streampark-common_2.11` | Maven | All versions | 2.0.0 | | `org.apache.streampark:streampark-common_2.12` | Maven | All versions | 2.0.0 | | `org.apache.streampark:streampark-common_2.12` | Maven | All versions | 2.0.0 | Products: Apache Streampark. ## How do I fix CVE-2022-45802? Upgrade org.apache.streampark:streampark-common_2.11 to 2.0.0 or later. ## Is CVE-2022-45802 being exploited? There is no known exploitation of CVE-2022-45802 in the wild and no public exploit code. ## Other vulnerabilities in Apache StreamPark (incubating) - [CVE-2024-29070](https://insights.sbomify.com/CVE-2024-29070/): Apache StreamPark: session not invalidated after logout (critical 9.1) - [CVE-2022-46365](https://insights.sbomify.com/CVE-2022-46365/): Apache StreamPark (incubating): Logic error causing any account reset (critical 9.1) - [CVE-2024-29178](https://insights.sbomify.com/CVE-2024-29178/): Apache StreamPark: FreeMarker SSTI RCE Vulnerability (high 8.8) - [CVE-2023-52291](https://insights.sbomify.com/CVE-2023-52291/): Apache StreamPark (incubating): Unchecked maven build params could trigger remote command execution (high 8.8) - [CVE-2024-29737](https://insights.sbomify.com/CVE-2024-29737/): Apache StreamPark (incubating): maven build params could trigger remote command execution (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-45802 and fix it if it is affected. What it is: CVE-2022-45802 is a critical vulnerability in Apache StreamPark (incubating), published on 1 May 2023. 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-2022-45802 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.streampark:streampark-common_2.11 (Maven): affected all versions; fixed in 2.0.0 - org.apache.streampark:streampark-common_2.11 (Maven): affected all versions; fixed in 2.0.0 - org.apache.streampark:streampark-common_2.12 (Maven): affected all versions; fixed in 2.0.0 - org.apache.streampark:streampark-common_2.12 (Maven): affected all versions; fixed in 2.0.0 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-2022-45802/ (Markdown: https://insights.sbomify.com/CVE-2022-45802/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-45802 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-45802 - OSV: https://osv.dev/vulnerability/CVE-2022-45802 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-45802/ Summaries are generated and may contain mistakes; the official description above is the record.