txt ?¬? le (for example, {1C82EAD9-
508E-11D1-8DCF-00C04FB951F9} from Figure 8-6) and paste it into the CLSID
?¬? eld. Then click Single.
5. If the program crashed during the fuzzing process of all CLSIDs or a single
CLSID, IE should stop and give control to WinDbg, which will print out the
exception. At this point, AxMan has identi?¬? ed an issue in which an ActiveX
property and/or method is not being properly handled, potentially allowing an
attacker to crash a user??™s system or even control their machine remotely. After
the crash on IE, switch back to WinDbg to view the exception.
Test ActiveX Controls for Buffer Over?¬‚ ows
The key to ensuring that your ActiveX controls will not be vulnerable to buffer overflow
attacks exposed by AxMan or axfuzz is to ensure that secure programming practices are
used. Additionally, using these tools in the QA phase of the software development life
cycle can also help ensure buffer overflows will not appear in production environments.
PROTECTING AGAINST UNSAFE
ACTIVEX OBJECTS WITH IE
An excellent method for ensuring that insecure ActiveX objects are not downloaded or
executed by IE is to modify the security setting for the browser.
Pages:
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388