BOVSTT is to detect the existence of remote/local stack-based buffer overflow vulnerabilities using the standard communication protocol for each service.
Overview
The application allows to customize the testing mechanism of each service through templates, these templates are simply plain text files, which accept some kind of special words (see STF section), these files are stored in the folder with a direct association between the protocol and the template and with the extension STF (Service Tester File).
Currently, the application version 2.1 supports the FTP, POP3 and SMTP protocol.To carry out this task the application allows specifying different types of parameters.
Also Read Brutespray – Port Scanning and automated Brute Force Tool
1.1 Parameters Buffer Overflow
1.1.1 Application Layer Protocol
Description: Specifies the type of protocol to be tested.
Required: Yes
Options: -ap –application-layer-protocol <protocol>
Accepted values: FTP, POP3 or SMTP
1.1.2 Target Hostname IP
Description: Specifies host / ip address to be tested
Required: Yes
Options: -th –target-hostname-ip
Accepted values: Any valid host / ip address.
1.1.3 Target Port
Description: Specifies the destination port of the service.
Required: No
Options: -tp –target-port <port>
Accepted values: 1 – 65535
If the user does not enter this parameter the application will automatically try to connect to the default
destination port according to the service and the type of encryption.
For example, for POP3 service and SSL encryption, the default port would be 995.
1.1.4 Cryptographic Security Protocol
Description: Specifies the type of service encryption.
Required: No
Options: -cp –cryptographic-security-protocol <crypt protocol>
Accepted values: SSL, TLS
Note: No support yet.
1.1.5 Login Username
Description: Specifies the user of the credentials.
Required: No
Options: -lu –login-username <username>
Accepted values: Alphanumeric value.
This parameter allows to customize the authentication mechanism of the protocol.
The application will initiate the authentication protocol through user / password as soon as it reads the
#AUTH macro within the STF file associated with the protocol. If the authentication by user / password fails,
the program will cancel its execution.
Every time the application reads the keyword <login-username> inside the STF file, it will be replaced by the
value of this parameter.
1.1.6 Login Password
Description: Specifies the password of the credentials.
Required: No
Options: -lu –login-password <password>
Accepted values: Alphanumeric value.
This parameter allows to customize the authentication mechanism of the protocol.
Every time the application reads the keyword <login-password> inside the STF file, it will be replaced by the
value of this parameter.
1.1.7 Buffer Overflow Size Length
Description: Specifies the buffer size.
Required: No
Options: -bs –buffer-size-length <size>
Accepted values: Numeric value greater than 0.
Default value: 4096
This parameter allows to customize the size of the buffer to send.
Every time the application reads the keyword <buffer> inside the STF file, it will be replaced by the sentence
{ –buffer-character } * { –buffer- size-length }, in this case for example A*4096.
1.1.8 Buffer Overflow Character
Description: Specifies the buffer character.
Required: No
Options: -bc –buffer-character <character>
Accepted values: Alphanumeric value.
Default value: ‘A’
1.1.9 Output Verbose
Description: Specifies whether the user wants to obtain more information during the negotiation process
with the remote host.
Required: No
Options: -ov –output-verbose
Accepted values: none
1.1.10 Credits
Description: View the author of the program.
Required: No
Options: -c –credits
Alone: Yes, cannot be combined with another parameter.
1.1.11 Version
Description: View the version of the program.
Required: No
Options: -v –version
Alone: Yes, cannot be combined with another parameter.
Compatibility
Currently, the system supports the Microsoft Windows platform and to generate the corresponding binary file only the Dev-C ++ IDE should be downloaded
- Platform: Microsoft Windows
- IDE: DEV-C ver-4.9.9.2
- Compiler: MinGW
- Dependences: Libwsock32.a (included in Dev-C++ IDE)
The Dev-C++ IDE can be downloaded from the following link.
Compilation
To compile the application the following steps must be taken
1. Installing the Dev-C ++ IDE: Go to the next link and run the setup.
https://sourceforge.net/projects/dev-cpp/files/Binaries/Dev-C%2B%2B%204.9.9.2/devcpp-
4.9.9.2_nomingw_setup.exe/download?use_mirror=netix&r=&use_mirror=netix
2. Download the GitHub project: Go to https://github.com/iricartb/buffer-overflow-vulnerabilityservices-tester-tool
and press the download button in the zip.
3. Unzip the zipped project using a decompression program.
4. Double click on the file BOVSTT.dev to load the Project.
5. In the Dev-C ++ IDE go to the Execute menu and click on the option to rebuild all (F12). If a dependency error occurs go to point 6, otherwise go to point 7. (Buffer Overflow) .
6. In the Dev-C ++ IDE go to the Project menu and click on the option Project options (1), later go to parameters tab (2) and delete the line that appears in the Linker section (3), then click on the add library button and finally find the libwsock32.a library in the lib folder of the Dev-C ++ IDE(5), select it and return to point 5.Buffer Overflow .
7. At this point, the BOVSTT.exe executable file should exist. Run the windows cmd.exe console and browse the filesystem until you find the project path.
8. Finally, run the BOVSTT.exe file with its parameters to start the test process.
In the following screenshot, you can see how the program detects the existence of a buffer overflow in the FTP service of the program FreeFloat FTP Server.
4. RUN THE PROGRAM WITHOUT COMPILATION
You can run the program without having to do the steps described in section 3, only with running the file BOVSTT.exe through windows console.
Author Credits
Author: Ivan Ricart Borges
Platform: Microsoft Windows
IDE: DEV-C ver-4.9.9.2
Compiler: MinGW
Dependences: Libwsock32.a
Version: 2.1
Project: https://github.com/iricartb/buffer-overflow-vulnerability-services-tester-tool
Mail: iricartb@gmail.com
Linkedin: https://www.linkedin.com/in/ivan-ricart-borges
Disclaimer
All the Content of this Article Belongs to above Original Author. “GBHackers On Security” won’t take any credits.This article is only for an Educational purpose.Any actions and or activities related to the material contained within this Website is solely your responsibility. The misuse of the information in this website can result in criminal charges brought against the persons in question.
The “Author” and “www.gbhackers.com” will not be held responsible in the event any criminal charges be brought against any individuals misusing the information in this website to break the law. Reproduce This Content Without Permission is Strictly Prohibited.
