GHSA-rrpj-r8h7-rm7r CVE-2024-43166
Apache DolphinScheduler Incorrect Default Permissions Vulnerability
- Severity
- 9.8 / 10
- Critical · CVSS 3.1
- Exploit chance (EPSS)
- 0.53%
- Chance of exploitation in the next 30 days. Higher than 45.04% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-276 Incorrect Default Permissions
- Fix
3.3.1- Upgrade org.apache.dolphinscheduler:dolphinscheduler to this version or later
Description
Incorrect Default Permissions vulnerability in Apache DolphinScheduler.
This issue affects Apache DolphinScheduler: before 3.2.2.
Users are recommended to upgrade to version 3.3.1, which fixes the issue.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.apache.dolphinscheduler:dolphinscheduler | < 3.3.1 |
3.3.1 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
org.apache.dolphinscheduler:dolphinscheduler Maven → 3.3.1
- maven
<dependency><groupId>org.apache.dolphinscheduler</groupId><artifactId>dolphinscheduler</artifactId><version>3.3.1</version></dependency>- gradle
implementation("org.apache.dolphinscheduler:dolphinscheduler:3.3.1")
Severity breakdown
CVSS 3.1 9.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-276: Incorrect Default Permissions
During installation, installed file permissions are set to allow anyone to modify those files.
How to prevent it
- Architecture and Design, Operation: The architecture needs to access and modification attributes for files to only those users who actually require those actions.
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-72mv-wwvm-vgp5 Apache DolphinScheduler has an Incorrect Authorization Vulnerability | High | Also affects org.apache.dolphinscheduler:dolphinscheduler |
| GHSA-f786-9c63-8xr8 Apache DolphinScheduler RPC module has a Deserialization of Untrusted Data vulnerability | Medium | Also affects org.apache.dolphinscheduler:dolphinscheduler |
| GHSA-3cjc-vhfm-ffp2 Apache DolphinScheduler vulnerable to sensitive information disclosure | High | Also affects org.apache.dolphinscheduler:dolphinscheduler |
| GHSA-3vcp-r62v-xpvg Apache DolphinScheduler vulnerable to Alert Script Attack | High | Also affects org.apache.dolphinscheduler:dolphinscheduler |
| GHSA-4vv4-crw4-8pcw Apache DolphinScheduler: Resource File Read And Write Vulnerability | High | Also affects org.apache.dolphinscheduler:dolphinscheduler |
| GHSA-m9q4-p56m-mc6q Apache DolphinScheduler: RCE by arbitrary js execution | High | Also affects org.apache.dolphinscheduler:dolphinscheduler |
| GHSA-ff2w-wm48-jhqj Arbitrary File Read Vulnerability in Apache Dolphinscheduler | High | Also affects org.apache.dolphinscheduler:dolphinscheduler |
| GHSA-vjqc-g788-f378 Session Fixation Apache DolphinScheduler | Medium | Also affects org.apache.dolphinscheduler:dolphinscheduler |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor