org.apache.dolphinscheduler:dolphinscheduler-api@3.0.1 vulnerabilities
latest version
3.2.1
latest non vulnerable version
first published
4 years ago
latest version published
10 months ago
licenses detected
- [1.2.0,)
package manager
Direct Vulnerabilities
Known vulnerabilities in the org.apache.dolphinscheduler:dolphinscheduler-api 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 Session Fixation. An attacker can hijack a user session by exploiting the fact that a session remains valid even after the user's password has been changed. How to fix Session Fixation? Upgrade | [,3.2.1) |
Affected versions of this package are vulnerable to Improper Control of Generation of Code ('Code Injection') due to improper validation of user-supplied input. An attacker can execute arbitrary code on the system by sending crafted requests to the affected component. How to fix Improper Control of Generation of Code ('Code Injection')? Upgrade | [3.0.0,3.2.1) |
Affected versions of this package are vulnerable to Missing Authorization allowing an authenticated user to delete UDFs in the resource center without proper permissions. How to fix Missing Authorization? Upgrade | [2.0.0,3.1.0) |
Affected versions of this package are vulnerable to Information Exposure. An attacker can gain unauthorized access to sensitive data by exploiting this vulnerability. How to fix Information Exposure? Upgrade | [,3.2.1) |
Affected versions of this package are vulnerable to Information Exposure due to the exposure of sensitive data to unauthorized actors. An attacker can access sensitive data such as database credentials by exploiting this vulnerability. How to fix Information Exposure? Upgrade | [3.0.0,3.0.2) |
Affected versions of this package are vulnerable to Improper Authentication such that an attacker can use a socket bytes attack to trigger this vulnerability. How to fix Improper Authentication? Upgrade | [3.0.0,3.1.2) |
Affected versions of this package are vulnerable to Improper Authentication due to insufficient checks in How to fix Improper Authentication? Upgrade | [,3.1.0) |