debugging - How are clientside security vulnerabilities generally discovered? -

I mean the only way in the operating system or their applications I can think of using dangerous tasks like strcpy () Binaries are examined, and then try to exploit those people, although with compiler improvements such as Visual Studio / GS Switch, this possibility will be mostly a matter of the past. Or am I making a mistake?

Do people use other ways to find weaknesses? Just load your target into a debugger, then send the unexpected input and see what happens?

Can some good books or websites be recommended on this subject?

Thanks in advance.

There are two major issues involved in "client side security"

most of today The common customer is used as "browser". Often memory corruption is responsible for vulnerabilities. ActiveX Com Objects has been a common path on the Windows system and has a good Active X phase.

In the context of memory protection systems / GS is a canary and it does not end the end of the buffer to prevent overflow. It is only to protect overflows based on those structures which are trying to overwrite the return address and control the EIP. NX Zone and Canaries are a good thing, but ASLR can be completely better in preventing the exploitation of memory corruption and the implementation of all the ASLRs is not uniformly secured. Even with these three systems, you are still being hacked. IE8, which runs on Windows 7, did all this and it was already hacked on PN-OOn and is here. It involved adding a heap overflow and dongling pointers vulnerability together.

A problem with "client side security" is created when the server side is reliant with a secret resource (such as a password) to the customer or send sensitive reports such as flash games in

The best way to see client side issues is by looking at traffic. Wireless is best for non-browser client / server protocols. However, you can use the best tools so far for browser based platforms like flash and javascript. Each case is going to separate, unlike buffer overflow, where this process is easy to see in the crash, client side problems are all about the context and to understand this problem a skilled person takes a look at the network traffic .

Sometimes foolhardy programmers will encrypt a password into their application. To get the data to diminish the app, its flash decimation is very neat, and you will also get full variable name and code comments. Another option is to use debugger like OLDDIbg to find and retrieve data in memory. IDA-Pro is the best decompile for C / C ++ applications