org.apache.streampark:streampark@2.1.0 vulnerabilities
latest version
2.1.5
first published
2 years ago
latest version published
4 months ago
licenses detected
- [2.0.0,)
package manager
Direct Vulnerabilities
Known vulnerabilities in the org.apache.streampark:streampark package. This does not include vulnerabilities belonging to this package’s dependencies.
How to fix?
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for free| Vulnerability | Vulnerable Version |
|---|---|
Affected versions of this package are vulnerable to Arbitrary Code Injection via the template processing mechanism. An attacker can execute arbitrary code on the server by injecting malicious templates after successfully logging into the system. How to fix Arbitrary Code Injection? Upgrade | [,2.1.4) |
Affected versions of this package are vulnerable to Arbitrary Command Injection due to insufficient validation of input parameters in the Note: This is only exploitable if the user has system-level permissions. How to fix Arbitrary Command Injection? Upgrade | [,2.1.4) |
Affected versions of this package are vulnerable to Arbitrary Command Injection due to improper validation of parameter input. An attacker can execute arbitrary commands by injecting malicious input into the build parameters. Note: This is only exploitable if the user has system-level permissions. How to fix Arbitrary Command Injection? Upgrade | [,2.1.4) |
Affected versions of this package are vulnerable to Insufficient Session Expiration due to improper session management. An attacker can maintain access and perform unauthorized actions by using the How to fix Insufficient Session Expiration? A fix was pushed into the | [0,) |
Affected versions of this package are vulnerable to SQL Injection through the How to fix SQL Injection? Upgrade | [2.0.0,2.1.4) |
Affected versions of this package are vulnerable to Improper Neutralization of Special Elements used in a Command ('Command Injection') due to insufficient validation of user-supplied input in the Maven compilation parameters. An attacker can execute arbitrary commands on the system by injecting malicious input into the build process. This is only exploitable if the attacker has logged in to the system with system-level permissions. How to fix Improper Neutralization of Special Elements used in a Command ('Command Injection')? Upgrade | [2.0.0,2.1.2) |
Affected versions of this package are vulnerable to SQL Injection. An attacker can cause information leakage by supplying malicious parameters to the How to fix SQL Injection? A fix was pushed into the | [0,) |