First off, is your 'airburst' user permitted to use sudo? You did not mention if it was working on your target system.
If not, everything is going to fail anyways. If I recall, sudo will even prompt for a password if you are not a permitted user or group and tell you afterwords that you dont have permissions to use sudo. You might need to check the settings in /etc/sudoers and the includes in /etc/sudoers.d, configure a group with some commands. The /etc/sudoers file actually has some commented setups that you can easily massage to your needs.
I got an analog of the scenario working using the bash built-in 'read'. Here is the short script that worked for me.
#!/bin/bash
read -s -p "pass? "
sudopas=${REPLY}; unset REPLY
#echo $sudopas | $(which sudo) --stdin ls -l /root/tmp
$(which sudo) ls -l /root/tmp
unset sudopas
To break this down; The read command grabs the password from the user through the 'pass?' prompt, that string is dumped into a variable. The $REPLY variable is unset (cleared). Then run sudo with the command we want. Then the variable containing the password is unset.
And when you run the command from another host;
$ ssh -t REMOTE_HOST '/bin/sh test.sh'
pass? total 0
-rw-r--r-- 1 root root 0 Apr 27 14:38 file1
-rw-r--r-- 1 root root 0 Apr 27 14:38 file2
-rw-r--r-- 1 root root 0 Apr 27 14:38 file3
-rw-r--r-- 1 root root 0 Apr 27 14:38 file4
Connection to REMOTE_HOST closed.
The ssh command line calls /bin/sh to execute the script. Using 'sudo --stdin' does work as well, but seems like its unnecessary since sudo already has that function. Using the 'sudo -t' flag should
Note that I have key based auth set up for my user between my testing hosts, hence no user and no password prompt for ssh. My user is in a primary group that is allowed to run commands using 'sudo', configured through /etc/sudoers.