Summary
Fluid vulnerable to OS Command Injection for Fluid Users with JuicefsRuntime
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]
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.
Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.
CVE-2023-51699 has a CVSS score of 4.0 (Medium). The vector is requires local access, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.9.3); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
For users who're using version < 0.9.3 with JuicefsRuntime， upgrade to v0.9.3.
Frequently Asked Questions
- What is CVE-2023-51699? CVE-2023-51699 is a medium-severity OS command injection vulnerability in github.com/fluid-cloudnative/fluid (go), affecting versions < 0.9.3. It is fixed in 0.9.3. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
- How severe is CVE-2023-51699? CVE-2023-51699 has a CVSS score of 4.0 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/fluid-cloudnative/fluid are affected by CVE-2023-51699? github.com/fluid-cloudnative/fluid (go) versions < 0.9.3 is affected.
- Is there a fix for CVE-2023-51699? Yes. CVE-2023-51699 is fixed in 0.9.3. Upgrade to this version or later.
- Is CVE-2023-51699 exploitable, and should I be worried? Whether CVE-2023-51699 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2023-51699 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2023-51699? Upgrade
github.com/fluid-cloudnative/fluidto 0.9.3 or later.