We??™ve
got packet captures, crash dumps, and proof of concept exploit code to help
you understand the exact nature of the problem.???
Vendor: ???All right, thanks, we will take care of that ASAP.???
Whether a vendor actually responds in such a positive manner is another matter. In fact,
if there is one truth in the vulnerability research business it??™s that dealing with vendors
can be one of the least rewarding phases of the entire process. The point is that you have
made it significantly easier for the vendor to reproduce and locate the problem and
increased the likelihood that it will get fixed.
Exploitability
Crashability and exploitability are vastly different things. The ability to crash an application
is, at a minimum, a form of denial of service. Unfortunately, depending on the
robustness of the application, the only person whose service youmay be denying could
be you. For true exploitability, you are really interested in injecting and executing your
own code within the vulnerable process. In the next few sections, we discuss some of the
things to look for to help you determine whether a crash can be turned into an exploit.
Debugging for Exploitation
Developing and testing a successful exploit can take time and patience.
Pages:
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804