Update payload.txt

pull/672/head
Aleff 2024-06-11 08:10:21 +02:00
parent 16c99038b2
commit 659312b2ec
1 changed files with 25 additions and 25 deletions

View File

@ -1,36 +1,36 @@
* REM #############################################################################################
* REM # #
* REM # Title : Auto-Check Cisco IOS XE Backdoor based on CVE-2023-20198 and CVE-2023-20273 #
* REM # Author : Aleff #
* REM # Version : 1.0 #
* REM # Category : incident-response #
* REM # Target : Cisco IOS XE #
* REM # #
* REM #############################################################################################
#############################################################################################
# #
# Title : Auto-Check Cisco IOS XE Backdoor based on CVE-2023-20198 and CVE-2023-20273 #
# Author : Aleff #
# Version : 1.0 #
# Category : incident-response #
# Target : Cisco IOS XE #
# #
#############################################################################################
ATTACKMODE HID
* REM VARIABLES
* REM 1) Set the script name editing $SCRIPT-NAME var, the default name is 'auto-check.sh' but you can change it here since is used the DuckyScript variable $SCRIPT-NAME.
# VARIABLES
# 1) Set the script name editing SCRIPT-NAME var, the default name is 'auto-check.sh' but you can change it here since is used the DuckyScript variable $SCRIPT-NAME.
SCRIPT-NAME='auto-check.sh'
* REM 2) Here you chould define the script path editing $PATH-TO-SCRIPT, if you don't change it is selected the default path, so the home path. If, for istance, you have a specific path where you put some stuff like this you can edit this DuckyScript variable with the correct path
# 2) Here you chould define the script path editing PATH-TO-SCRIPT, if you don't change it is selected the default path, so the home path. If, for istance, you have a specific path where you put some stuff like this you can edit this DuckyScript variable with the correct path
PATH-TO-SCRIPT='~/'
* REM 3) Replacing `here` you must set your sudo password that permit to give the executable permissions to the file
# 3) Replacing `here` you must set your sudo password that permit to give the executable permissions to the file
SUDO-PSWD='here'
QUACK DELAY 3000
QUACK DELAY 1500
QUACK CTRL-ALT t
QUACK DELAY 1000
QUACK STRING echo 'while true; do
QUACK ENTER
QUACK DELAY 500
QUACK STRING response=$(curl -k -H \"Authorization: 0ff4fbf0ecffa77ce8d3852a29263e263838e9bb\" -X POST https://systemip/webui/logoutconfirm.html?logon_hash=1)
QUACK STRING response=\$(curl -k -H \"Authorization: 0ff4fbf0ecffa77ce8d3852a29263e263838e9bb\" -X POST https://systemip/webui/logoutconfirm.html?logon_hash=1)
QUACK ENTER
QUACK DELAY 500
QUACK STRING if [[ $response =~ ^[0-9a-zA-Z]+$ ]]; then
QUACK STRING if [[ \$response =~ ^[0-9a-zA-Z]+\$ ]]; then
QUACK ENTER
QUACK DELAY 500
QUACK STRING if [ $? -eq 0]; then
QUACK STRING if [ \$? -eq 0]; then
QUACK ENTER
QUACK DELAY 500
@ -86,18 +86,18 @@ QUACK STRING done' > $PATH-TO-SCRIPT$SCRIPT-NAME
QUACK ENTER
QUACK DELAY 500
* REM To avoid some bad DELAY I decided to use only one command row
# To avoid some bad DELAY I decided to use only one command row
QUACK REM Old script
* REM STRINGLN sudo chmod +x $SCRIPT-NAME
* REM DELAY 500
* REM STRINGLN $SUDO-PSWD
* REM DELAY 3000
* REM STRINGLN sh $PATH-TO-SCRIPT$SCRIPT-NAME $
* REM STRINGLN exit
# STRINGLN sudo chmod +x $SCRIPT-NAME
# DELAY 500
# STRINGLN $SUDO-PSWD
# DELAY 3000
# STRINGLN sh $PATH-TO-SCRIPT$SCRIPT-NAME \$
# STRINGLN exit
QUACK REM Optimized script
QUACK STRING sudo chmod +x $SCRIPT-NAME; sh $PATH-TO-SCRIPT$SCRIPT-NAME $; exit
QUACK STRING sudo chmod +x $SCRIPT-NAME; sh $PATH-TO-SCRIPT$SCRIPT-NAME \$; exit
QUACK ENTER
QUACK DELAY 500
QUACK STRING $SUDO-PSWD