Skip to content

Fluid vulnerable to OS Command Injection for Fluid Users with JuicefsRuntime

Moderate severity GitHub Reviewed Published Mar 15, 2024 in fluid-cloudnative/fluid • Updated Mar 25, 2024

Package

gomod github.com/fluid-cloudnative/fluid (Go)

Affected versions

< 0.9.3

Patched versions

0.9.3

Description

Impact

OS command injection vulnerability within the Fluid project's JuicefsRuntime can potentially allow an authenticated user, who has the authority to create or update the K8s CRD Dataset/JuicefsRuntime, to execute arbitrary OS commands within the juicefs related containers. This could lead to unauthorized access, modification or deletion of data.

Patches

For users who're using version < 0.9.3 with JuicefsRuntime， upgrade to v0.9.3.

References

Are there any links users can visit to find out more?

Credits

Special thanks to the discovers of this issue:

Xiaozheng Zhang [email protected]

References

@cheyang cheyang published to fluid-cloudnative/fluid Mar 15, 2024
Published to the GitHub Advisory Database Mar 15, 2024
Reviewed Mar 15, 2024
Published by the National Vulnerability Database Mar 15, 2024
Last updated Mar 25, 2024

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
Local
Attack complexity
High
Privileges required
High
User interaction
Required
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:L/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N

EPSS score

0.043%
(11th percentile)

Weaknesses

CVE ID

CVE-2023-51699

GHSA ID

GHSA-wx8q-4gm9-rj2g

Source code

Credits

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