
Thick client application VAPT for locally installed risk
Because the real threat is already inside the machine

A thick client vulnerability assessment and penetration test (VAPT) is a security assessment of locally installed desktop applications. It examines the application GUI, file system, registry, memory, and network communication to identify and exploit security vulnerabilities. Unlike a web application penetration test, a thick client VAPT targets client-side binary execution, runtime memory manipulation, and DLL preloading. Swarmnetics delivers this application security service through Offensive Security Certified Professional (OSCP) and CREST Registered Penetration Tester (CRT) certified consultants.

When client applications become attack paths
Reverse engineering the truth: Where weakness becomes insight

In February 2024, Microsoft disclosed CVE-2024-21413, a critical vulnerability in the Microsoft Outlook desktop client, after in-the-wild exploitation. The flaw was later added to CISA’s Known Exploited Vulnerabilities Catalog. NVD identifies it as a Microsoft Outlook remote code execution vulnerability and records a CVSS score of 9.8. The issue showed how a trusted desktop client could become an attack path on the endpoint, rather than just a front end to backend systems. A thick client application penetration testing engagement would have identified unsafe link handling in the desktop application before exploitation.
Organisations often need to validate application security controls through regular testing. Thick client applications are routinely excluded from security testing programmes because teams assume internal deployment means lower risk. That assumption overlooks what a malicious insider or compromised workstation can access through local files, memory, registry artefacts, and client-side trust decisions that web application testing never touches. That blind spot creates cyber threats that routine security assessments often miss.

Assessing the desktop attack path
Tracing client-to-server flaws to stop real exploits

Our OSCP and CREST-certified consultants test thick client apps on both a black-box basis and a grey-box basis. Black-box testing simulates an attacker on a compromised endpoint with no prior knowledge of the application. Grey-box testing uses architecture documentation and test credentials to increase coverage of authenticated workflows and backend server interactions.
The assessment starts with information gathering on the application architecture, technologies, and entry points. It examines local files, memory, registry artefacts, and configuration weaknesses that affect the desktop runtime. It also reviews network communication to ensure the robustness and integrity of thick client software and its communication protocols. The work follows the CWE/SANS Top 25 Most Dangerous Software Errors and the OWASP Desktop App Security Top 10. Our consultants use manual testing with Burp Suite Professional, dnSpy, DotPeek, Process Hacker, the Sysinternals Suite, Regshot, Wireshark, and PESecurity. This thick client app penetration testing approach helps us reverse engineer .NET assemblies. It also identifies logic flaws from a real-world attack perspective. That allows us to uncover hardcoded credentials, insecure local storage, weak DLL loading behaviour, and client-side business logic that can be bypassed from the endpoint. A thick client app VAPT is designed to uncover weaknesses in desktop applications that routine testing often misses.
Yes, we are CREST accredited
Our core team is based in Singapore and consists of CREST certified penetration testers who are also Offensive Security Certified Professional (OSCP) certified. The team has delivered numerous penetration testing projects for customers in Singapore and other locations, from large multinational enterprises to small and medium business, and across various industries.

Inside the thick client attack surface
From findings to fortitude: the real outcome of testing

A thick client VAPT covers the following scope items across the full tier architecture of desktop applications. The list below focuses on local attack surfaces, sensitive data exposure, sensitive information in local artefacts, application server interaction, and paths that can permit unauthorized access.
- Application architecture mapping — authentication and authorisation mechanism review
- GUI object permissions — hidden object disclosure, disabled functionality activation, and masked password exposure
- File and folder permissions — strong naming verification, code signing authentication, and DLL preloading and backdoor insertion
- Registry access — read and write permission review, and authentication bypass through registry manipulation
- Application memory — process replacement, assembly modification, and debug breakpoint testing to identify dangerous functions
- Network traffic — HTTP and HTTPS inspection, firewall rule bypass, and man-in-the-middle susceptibility across client-side and server side communication
- Assembly protections — ASLR, SafeSEH, DEP, ControlFlowGuard, and HighEntropyVA verification
- Client control bypass — business logic abuse, privilege escalation through GUI control bypass, and authorisation validation


