org.apache.streampark:streampark vulnerabilities
StreamPark, Make stream processing easier! easy-to-use streaming application development framework and operation platform
- Registry
- Maven
- Latest
- 2.1.5
- License
- The Apache License, Version 2.0
12 known advisories
The latest version, 2.1.5, is affected by 4 of them.
Is your project on an affected org.apache.streampark:streampark?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.apache.streampark:streampark
Apache StreamPark: Use the user’s password as the secret key Vulnerability
- Affected
- >=2.0.0 <2.1.7
- Fixed in
- 2.1.7
Apache StreamPark uses a Weak Encryption Algorithm
- Affected
- >=2.0.0 <2.1.7
- Fixed in
- 2.1.7
Apache StreamPark has a hard-coded encryption key
- Affected
- >=2.0.0 <2.1.7
- Fixed in
- 2.1.7
Apache StreamPark contains an Incorrect Execution-Assigned Permissions vulnerability
- Affected
- <=2.1.5
- Fixed in
- No fix released
Apache StreamPark: FreeMarker SSTI RCE Vulnerability
- Affected
- <2.1.4
- Fixed in
- 2.1.4
Apache StreamPark: Information leakage vulnerability
- Affected
- >=2.0.0 <2.1.4
- Fixed in
- 2.1.4
Apache StreamPark: maven build params could trigger remote command execution
- Affected
- <2.1.4
- Fixed in
- 2.1.4
Apache StreamPark: Unchecked maven build params could trigger remote command execution
- Affected
- <2.1.4
- Fixed in
- 2.1.4
Apache StreamPark: Authenticated system users could trigger remote command execution
- Affected
- >=2.0.0 <2.1.2
- Fixed in
- 2.1.2
Apache StreamPark: Authenticated system users could trigger SQL injection vulnerability
- Affected
- >=2.0.0 <2.1.2
- Fixed in
- 2.1.2
Apache StreamPark Improper Input Validation vulnerability
- Affected
- >=1.0.0 <2.0.0
- Fixed in
- 2.0.0
Apache StreamPark LDAP Injection vulnerability
- Affected
- >=1.0.0 <2.0.0
- Fixed in
- 2.0.0
Is your org.apache.streampark:streampark version vulnerable?
Which of your client projects still run an old org.apache.streampark:streampark?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.