Adblock Detected

Read

[SET v5.2] The Social-Engineer Toolkit "Urban Camping"

Read

The Social-Engineer Toolkit (SET) version 5.2 codename “Urban Camping” has been released. This version adds a complete rewrite of the PowerShell injection techniques within SET and incorporates an automatic process downgrade attack detailed here: https://www.trustedsec.com/may-2013/native-powershell-x86-shellcode-injection-on-64-bit-platforms/. The attack will automatically detect if PowerShell is installed, then detect what platform its running on. If 64 bit is detected, it will automatically downgrade the process to a 32 bit process for native shellcode injection.

Changelog

* incorporated the new x86 PowerShell downgrade attack. This will automatically use x86 shellcode regardless of operating system. (https://www.trustedsec.com/may-2013/native-powershell-x86-shellcode-injection-on-64-bit-platforms/)

* changed platform detection from if($env:PROCESSOR_ARCHITECTURE -eq “AMD64″) to [IntPtr]::Size -eq 6 (thanks Matthew Graeber)

* rewrote payload generator in powershell menu to use new process downgrade attack

* rewrote java applet to use the new process downgrade attack

* rewrote powershell generation within setcore to use the powershell downgrade attack

* changed the default Java Applet wording to “Applet verified as safe (TRUSTED)”.

* fixed a bug that would cause SQL bruter to error out when specifying a single host and the host was not alive

* fixed a bug that would allow you use web templates with webjacking and tabnabbing which it should not have

* removed old encoding methods when using standard metasploit executables

* fixed an issue that would not allow SSL and harvester to work correctly – this required manually patching socket.py and keeping a patched version in the root directory upon launch. This is due to a bug in pyopenssl and unhandled packet handling within socket.py

* added more stability to the SSL harvester when using pem certificate files

* added powershell downgrade attack to psexec powershell attack

* added ExitOnSession to false when using psexec command

* added set EnableStageEncoding true when using psexec command for stager encoding with shikata

* added better stability to the powershell injection attacks with multiple detection points

* fixed an issue that would cause an error message when reusing credential harvester

* added proper cleanup on new socket.py – has to be in SET root – weird issue when os.chdir or sys.path.append – doesn’t recognize

* removed man left in the middle from the web attacks menu

* streched the text on the menu to be full line versus manual splitting

* added new code and binary for pyinjector to evade AV

* added new code and binary for multipyinjector to evade AV

* officially removed the “set” command and moved to se-toolkit, set was a linux command and conflicted – use se-toolkit from here on out

* simplified the replace code for the shellcode powershell injection technique in setcore

* improved string encryption on the java applet attack

* added -noprofile flag option to powershell injection for x86 downgrade attack

* slimmed down the code used for the powershell injection attacks, allows more space for shellcode

Download SET v5.2

[SET v5.1] The Social-Engineer Toolkit codename “Name of the Doctor”

Read

Download SET v5.1 “Name of the Doctor”

The Social-Engineer Toolkit (SET) version 5.1 codename “Name of the Doctor” has been released. This version adds a complete rewrite of the MSSQL Bruter as well as a new attack vector utilizing the PSExec functionality within Metasploit.

The MSSQL Bruter now incorporates UDP port 1434 quick discovery by sending a specially crafted packet to MSSQL servers and returning the port automatically. This technique eliminates the need to port scan and quickly identifies the SQL server as well as what port the SQL server is listening on. In addition, SET has moved away from the _mssql python module and towards impacket from Core Security. Main reason for this is due to some instabilities in later versions of _mssql with execute_query() being broke as well as the functionality built into impacket makes it much easier to use.

In addition to utilizing impacket, originally in SET you had two options for payload delivery, the first being POwerShell and the second the binary 2 hex debug conversion attack vector. This has been changed to automatically detect if PowerShell is installed on the victim machine, if it is – SET will automatically deploy a PowerShell injection technique that has been completely rewritten in the MSSQL module. If it does not detect PowerShell, it will automatically revert back to the debug. Lastly on the MSSQL Bruter portions, performance has been increased significantly on the brute forcing, discovery, and deploying of payloads.

For a video of the features, check out below:

Vimeo: Video

A new attack vector build into SET is the new psexec attack vector inside the Fast-Track menu. During a penetration test, often times you may have credentials to a server and want Meterpreter on a wide scale level. The psexec traditional module gets picked up by Anti-Virus due to known signatures being used. You can either use the EXE::Custom advanced feature however it still doesn’t give you the ability to select RHOSTS (multiple IP addresses) unless you custom script it or through something like railgun. The newer module “psexec_command” allows you to specify RHOSTS as well as execute a command on the operating system. Inside of SET, the psexec attack vector will automatically created a meterpreter backdoor through PowerShell and deploy it to systems you have permission to (RHOSTS). You can either use a username and password that you’ve decrypted or the hash for the pass the hash attack vector.

In addition to the new attack vectors, a number of other improvements, bug fixes, and enhancements have been made in this release. For more on all of the changes, check out the changelog before:

Changelog v5.1

when specifying a custom wordlist in SET – added the ability for ports to be specified ipaddr:portnum for example 192.168.5.5:2052 just in case a SQL server is not listening on 1433
incorporated udp port 1434 enumeration instead of portscanning – much more faster and efficent – also finds ports that are not on port 1433 (thanks Larry Spohn)
removed the src/core/portscan.py it is no longer needed
added impacket as a dependacy – will be used for psexec command execution and TDS connections via mssql
fixed an issue that would cause the import modules to not load properly when relaunching the MSSQL Brute attack
improved the speed of the MSSQL brute attack on initial brute force
completely rewrote MSSQL Brute to incorporate impacket – SET no longer uses the _mssql module – highly buggy in the latest versions
improved udp 1434 detection capability by piping through the printCIDR function which will utilize CIDR notations when scanning
incorporated new function called capture which will take stdout from function calls and present them as a string – important when doing regex in impacket
streamlined the MSSQL bruter to automatically profile the system to determine if Powershell is installed, if so it will automatically do powershell injection, if not it will fall back to the Windows debug method for payload delivery
rewrote the entire powershell deployment module – it now ties in to standard powershell shell payload delivery system
added dynamic shellcode patching to the MSSQL bruter – now generates shellcode automatically, cast it unicode, then base64 encoding for EncodedCommand powershell bypass technique
rewrote the hex2binary deployment method to support the new impacket method – it will now automatically deliver a binary based on the attack vector that you want to use
shrunk the powershell injection code to fit properly within MSSQL xp_cmdshell one call
added one line for xp_cmdshell disable which works on later versions of Windows
removed the portscan functionality completely out of the MSSQL payload
rewrote all portions of the MSSQL bruter to be fully impacket and removed the dependacy for _mssql from fast-track
added new attack vector within the Fast-Track menu “PSEXEC Powershell Injection” which will allow you to specify psexec_command and compromise via direct memory injection
added ability to set threads within the new PSEXEC PowerShell Injection technique
added quick dynamic patching for the powershell injection technique for payloads
added a new trustedsec intro ascii art that has the TS logo on it
updated rid_enum to the latest github version inside SET

[SET Version 5.0] The Social-Engineer Toolkit "The Wild West"

Read

Download The Social-Engineer Toolkit (SET) v5.0

Social-Engineer Toolkit (SET) v5.0 codename: The Wild West is a culmination of six months of development, bug squashing, and user feedback. New with this version includes a completely redesigned multiprocessing web server that handles non-rfc compliant HTTP information. The builtin SET web server would on occasion crash when receiving unexpected characters. The new version of the web server is stable, and significantly faster. This version if Kali Linux compliant (FSH) where all information is now moved and removed from src/program_junk and to your ~/.set home directory.

In addition to FSH structuring of SET, we have also added some significant performance and stability updates. For example, traditionally if you launched an attack, you would have to exit out of SET completely then relaunch. The dynamic importing has now changed to fix this and improve the ability to reuse modules.

For a full list of changes, the changelog can be found below:

~~~~~~~~~~~~~~~~

version 5.0

~~~~~~~~~~~~~~~~

* fixed a bug that would cause tabnabbing to throw an exceptions around check_options

* added setcore modules into tabnabbing to allow centralized routines

* fixed a bug that would cause webjacking to throw an exeptions around check_options

* added git clean -fd prior to set update, this will force a clean when pulling the latest files

* fixed a bug that would cause a system not setup properly when installing in setup.py

* fixed a bug on start_dns() upon launch will cause errors on certain systems

* added installation script for putting SET into /usr/bin and /usr/share for FSH compliant installer

* added set-update to the installation path, can type that anywhere now

* added set-automate to the list to be typed in anywhere

* fixed a bug that would cause the java applet method to not work a second time in use (reload)

* rewrote MASSIVE amounts of code to no longer use src/program_junk for storage of applications, its now all under ~./set

* fixed a os.chdir issue when using it to spawn a web server during java applet, moved to multi processing instead of threading.thread

* fixed a bug that caused credential harvester to throw an exceptions with the new ~./.set directory structure

* centralized setdir into the main repository to handle it through there and to call the ~/.set directory

* added additional passwords to wordlist.txt used for fast-track mssql brute forcing

* fixed a mssql access bug that would cause fast-track to error out if unspecified IP was added

* removed the pymssql check from the initial SET start and onto Fast-Track since it’s only used there

* turned java repeater to ON by default, much better success rate in SE pentesting

* rewrote large portions of payloadgen to incorporate the changes to the new ~/.set path variables

* added a new file structure to launch set called se-toolkit. The set executable is now depricated and should no longer be used – to launch set just type ./se-toolkit

* updated the setup.py installation to be more robust when performing installations (windows, etc.)

* moved all of the reporting structures within SET to the new ~/.set directory

* added a checkup routine in set and se-toolkit to check for the reports directory

* fixed a bug that would cause multi powershell injection to trigger even when using the powershell menu, it will just generate one now

* fixed an issue that could cause powershell injection to not work properly using the fast patch method

* fixed an issue that would cause definepath to not be specified when using the SE Toolkit Interactive shell

* fixed relative path issues in sccm_main and powershell teensy vectors to point to new .set directory

* fixed an issue that would cause the SE toolkit to hang on a weird bug when importing binascii – moved binascii to main import above and no longer hung

* fixed a before assignment error when using the windows debug conversion in the fast-track mssql menu (meta_path reference)

* changed reports directory within the teensy side to move to ~/.set/reports

* moved the report_generator in harvester to pull and report on the new ~/.set reports structure

* fixed an issue where webjacking would not post properly on certain websites (index2.html conflict issue)

* added the Metasploit MS13-009-IE SLayoutrun Use After Free Exploit to the Metasploit Brwoser Exploit attacks

* fixed a parsing issue with the JMX bean exploit in the SET menu text from appearing to be on one line

* added a new description on setting up sendmail for Kali Linux

* added a check for multi powershell injection and check for solo instances through powershell teensy and not to generate a ton

* changed the email handler from control-c to END instead. Control-C will break multiprocessing within src.html.spawn and this is the proper way to do it

* cleaned up setcore with old code and optimized other areas of the code base

* reduced the description of the allports payload when selecting in web attack method

* added a completely new and redesigned multi threaded and multiprocessing web server – should be significantly faster with less bugs and crashing when handling non-rfc compliant HTTP requests

* optimized applet load time to be much more efficent when being loaded into the web attack vector (about 4 seconds improvement)

* rewrote exceptions handler for the new web server to check to see if anything is running on port 80 when starting

* turned java repeater to on by default – more stable and tested on multiple platforms

* fixed an issue that would cause the java applet web cloner to fail upon running it twice – added reload(module) option to fix the bug

* fixed an issue that caused powershell.prep to not load if used twice

* fixed an import error when using powershell injection through the main menu

* changed initial set menu in powershell to be the standard setprompt

* changed the default port to 443 on powershell delivery in the set option number 10

* fixed an issue that would cause the powershell injection to spawn on port 22 versus 443 as specified

* removed the man left in the middle attack – no longer in use, outdated and not maintained

* removed beautifulsoup as a dependancy for SET due to the removal of man left in the middle

* added the ability to call the web server and stop it based on stop_server()

[SET v4.7] The Social-Engineer Toolkit

Read