[REVS] Bugger The Debugger
SecuriTeam <[email protected]>
| Newsgroups | gmane.comp.security.securiteam |
|---|---|
| Message-ID | <[email protected]> |
The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com - - promotion The SecuriTeam alerts list - Free, Accurate, Independent. Get your security news from a reliable source. http://www.securiteam.com/mailinglist.html - - - - - - - - - Bugger The Debugger ------------------------------------------------------------------------ SUMMARY The paper linked below will demonstrate methods that may be used by malware to execute code, simply by being loaded into a debugging session. This code execution occurs before the debugger passes control back to the user and therefore cannot be prevented. DETAILS Abstract: The use of debuggers to analyse malicious or otherwise unknown binaries has become a requirement for reverse engineering executables to help determine their purpose. While researchers in places such as anti-virus laboratories have always done this, with the availability of free and easy to use debuggers it has also become popular with corporate security officers and home users. One of the main purposes of a debugger is to allow the user to control the execution of a binary in such a way as to determine what instructions or commands the binary is executing. During malware analysis the user can modify what the binary is trying to execute, or prevent it all together. ADDITIONAL INFORMATION The information has been provided by <mailto:[email protected]> Brett Moore. The original article can be found at: <http://www.security-assessment.com/Whitepapers/PreDebug.pdf> http://www.security-assessment.com/Whitepapers/PreDebug.pdf ======================================== This bulletin is sent to members of the SecuriTeam mailing list. To unsubscribe from the list, send mail with an empty subject line and body to: [email protected] In order to subscribe to the mailing list, simply forward this email to: [email protected] ==================== ==================== DISCLAIMER: The information in this bulletin is provided "AS IS" without warranty of any kind. In no event shall we be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages.