Skip to content

Apache DolphinScheduler vulnerable to Path Traversal

Moderate severity GitHub Reviewed Published Oct 28, 2022 to the GitHub Advisory Database • Updated Jan 30, 2023

Package

maven org.apache.dolphinscheduler:dolphinscheduler (Maven)

Affected versions

< 2.0.6

Patched versions

2.0.6

Description

Users can read any files by log server, Apache DolphinScheduler users should upgrade to version 2.0.6 or higher.

References

Published by the National Vulnerability Database Oct 28, 2022
Published to the GitHub Advisory Database Oct 28, 2022
Reviewed Oct 31, 2022
Last updated Jan 30, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.052%
(23rd percentile)

Weaknesses

CVE ID

CVE-2022-26884

GHSA ID

GHSA-vpgf-fgm8-gxr2

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.