Thick Client Application Penetration Testing

• Weekdays - 5 to 6 weeks
• Weekend - 6 to 7 weeks
• FastTrack - 4 to 5 weeks

• Weekdays - 5 to 6 weeks
• Weekend - 6 to 7 weeks
• FastTrack - 4 to 5 weeks

• Overview About Thick Client Application Security Course
• Introduction to basics of thick client application security

• Two-Tier architecture
• Three-Tier architecture

• Information Gathering Introduction
• Application Architecture and Identifying the Languages and Frameworks Used
• Network Communication Between the Client and the Server

• Use of sysinternals suite and commonly used tools
• Looking for secret using strings, process hacker and checking Configuration

• Files Analysis
• Identifying DLL Hijacking Vulnerability
• Identifying Interesting Files Bundled with the Thick Client Application
• Binary Analysis
• Weak Graphical User Interface
• Memory Analysis

• Reverse Engineering using dnSpy and cracking database password
• Recompiling using dnSpy after modification

• OWASP TOP10 Vulnerabilities

• Conducting Injection Attack Manually

• Network Tools overview and demo
• Intercepting and modifying with echo mirage | Burp suite
• Packet manipulating and attacking with scapy
• Network monitor tool for intercepting process traffic (demo)

• Explanation on ASLR , DEP and GET- PE-security Demo
• Checking for Sensitive data in Registry with Regshot
• Binskim| Binscope | Fxcop Demo for developer Usage

• Dll Hijacking with Procmon and Msfvenom
• PowerSploit to Automate Dll Hijacking

• Debugging to Bypass Security Controls
• Debugging with DnSpy for admin login

Problem Statement: - Develop a manual testing process for detecting missing or ineffective access control.

Description: - Exploiting access control is one of favourite approach that an attacker uses to practice. Access control is detectable using manual means or through automation. It’s weakness primarily because of lack of automated detection and lack of effective functional testing by application developers. Manual testing is best way to detect missing or ineffective access control including HTTP method (GET or PUT), controller, direct object references etc.

Problem Statement: - Develop a process to identify any injection flaw in your mobile application.

Description: - Injection flaws are a class of vulnerability that allow a user to breakout of application context. If your application takes user input and inserts it into a back-end database, shell command or operating system call then your application may be susceptible to an injection flaw. To avoid it before calling external function verify that the data is what you expect i.e. execute a validation function. There are certain exception such as Single Quotes (‘) are valid character on people’s last names. However, if you allow a single quote in a last name field, you can be introducing SQL injection into your application.

Problem Statement: - Make a DoS attack to test any such possible vulnerability

Description: - Denial-of-Service (DoS) is a type of cyber-attack in which one make an attack over a system and interrupt the device’s normal functioning. DoS attacks done by flooding a target device with traffic or information which can trigger a crash. DoS attack deprives the target users of the service they expected. You need to test the mobile device against any possible DoS attack and make sure device can withstand any possible attack.