Huajie Wang

**Name of the Vulnerable Software and Affected Versions** Streampark versions prior to 2.1.2 **Description** The issue arises in the Streampark platform when users log in and utilize certain features, specifically those providing name-based fuzzy search functionality for items like job names and role names. The SQL syntax used is `select * from table where jobName like '%jobName%'`. However, the `jobName` field is susceptible to receiving illegal parameters, which can lead to SQL injection and potentially result in information leakage. **Recommendations** For versions prior to 2.1.2, users are recommended to upgrade to version 2.1.2, which fixes the issue. As a temporary workaround, consider restricting the use of the fuzzy search feature until the upgrade is applied. Additionally, users should avoid using the `jobName` field in the affected SQL syntax until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** streampark versions prior to 2.1.2 **Description** The issue is related to the project module in streampark that integrates Maven's compilation capability. There is no check on the compilation parameters of Maven, allowing attackers to insert commands for remote command execution. The prerequisite for a successful attack is that the user needs to log in to the streampark system and have system-level permissions. Generally, only users of that system have the authorization to log in, and users would not manually input a dangerous operation command. Therefore, the risk level of this issue is very low. **Recommendations** All users should upgrade to 2.1.2 to mitigate the risk. As a temporary workaround, consider restricting access to the Maven compilation parameters to minimize the risk of exploitation. Avoid using the `settings.xml` file in the `/usr/share/java/maven-3/conf/` directory with untrusted input until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Apache StreamPark versions prior to 2.0.0 **Description** The issue allows any user to upload a jar as an application without mandatory verification of the uploaded file type. This enables users to upload high-risk files and potentially upload them to any directory. **Recommendations** For versions prior to 2.0.0, upgrade to Apache StreamPark 2.0.0 or later. As a temporary workaround, consider restricting the upload functionality to prevent users from uploading high-risk files until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Apache StreamPark versions 1.0.0 through 1.0.0 **Description** The issue arises when a user successfully logs in and attempts to modify their profile. The `username` is passed to the server-layer as a parameter but is not verified to ensure it matches the currently logged-in user or if the user is legitimate. This oversight allows malicious attackers to send any `username` to modify and reset the account. **Recommendations** For Apache StreamPark versions 1.0.0, upgrade to Apache StreamPark 2.0.0 or later.

**Name of the Vulnerable Software and Affected Versions** Apache StreamPark versions 1.0.0 through 2.0.0 **Description** The issue is related to an LDAP injection vulnerability, which is an attack used to exploit web-based applications that construct LDAP statements based on user input. When an application fails to properly sanitize user input, it's possible to modify LDAP statements through techniques similar to SQL Injection. This could result in the granting of permissions to unauthorized queries and content modification inside the LDAP tree. The risk may only occur when the user logs in with LDAP, and the user name and password login will not be affected. **Recommendations** For Apache StreamPark versions 1.0.0 through 2.0.0, upgrade to Apache StreamPark 2.0.0 or later to resolve the issue. As a temporary workaround, consider restricting access to the LDAP functionality until the upgrade is applied. Additionally, users should be cautious when logging in with LDAP to minimize the risk of exploitation.