Streampark vulnerabilities
10 known vulnerabilities in Streampark from Apache. 10 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 7.5 High severity
Apache StreamPark: Use of a Broken or Risky Cryptographic Algorithm
Weak Encryption Algorithm in StreamPark, The use of an AES cipher in ECB mode and a weak random number generator for encrypting sensitive data, including JWT tokens, may have risked exposing sensitive authentication data This issue affects Apache StreamPark: f
- 9.8 Critical severity
Apache StreamPark: Use of Hard-coded Credentials
In Apache StreamPark versions 2.0.0 through 2.1.7, a security vulnerability involving a hard-coded encryption key exists. This vulnerability occurs because the system uses a fixed, immutable key for encryption instead of dynamically generating or securely conf
- 7.3 High severity
Apache StreamPark: Incorrect Execution-Assigned Permissions
Incorrect Execution-Assigned Permissions vulnerability in Apache StreamPark. This issue affects Apache StreamPark: from 2.1.4 before 2.1.6. Users are recommended to upgrade to version 2.1.6, which fixes the issue.
- 7.6 High severity
Apache StreamPark: Improper Neutralization of Special Elements used in an SQL Command
SQL Injection vulnerability in Apache StreamPark. This issue affects Apache StreamPark: from 2.1.4 before 2.1.6. Users are recommended to upgrade to version 2.1.6, which fixes the issue. This vulnerability is present only in the distribution package (SpringBoo
- 9.1 Critical severity
On versions before 2.1.4, session is not invalidated after logout.
On versions before 2.1.4, session is not invalidated after logout. When the user logged in successfully, the Backend service returns "Authorization" as the front-end authentication credential. "Authorization" can still initiate requests and access data even af
- 8.8 High severity
Apache StreamPark: Improper Control of Generation of Code
On versions before 2.1.4, a user could log in and perform a template injection attack resulting in Remote Code Execution on the server, The attacker must successfully log into the system to launch an attack, so this is a moderate-impact vulnerability. Mitigati
- 8.1 High severity
Apache StreamPark (incubating): Improper Neutralization of Special Elements used in an SQL Command
In streampark-console the list pages(e.g: application pages), users can sort page by field. This sort field is sent from the front-end to the back-end, and the SQL query is generated using this field. However, because this sort field isn't validated, there is
- 7.2 High severity
Apache StreamPark (incubating): Improper Neutralization of Special Elements used in a Command
In streampark, there is a project module that integrates Maven's compilation capability. However, there is no check on the compilation parameters of Maven. allowing attackers to insert commands for remote command execution, The prerequisite for a successful at
- 9.1 Critical severity
Apache StreamPark 1.0.0 before 2.0.0 When the user successfully logs in, to modify his…
Apache StreamPark 1.0.0 before 2.0.0 When the user successfully logs in, to modify his profile, the username will be passed to the server-layer as a parameter, but not verified whether the user name is the currently logged user and whether the user is legal, T
- 9.8 Critical severity
Apache StreamPark (incubating): Unrestricted Upload of File with Dangerous Type
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 A