[REVS] How Shellcodes Work
- From: SecuriTeam <support@xxxxxxxxxxxxxx>
- Date: 24 May 2006 14:00:47 +0200
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
- - - - - - - - -
How Shellcodes Work
------------------------------------------------------------------------
SUMMARY
Peter Mikhalenko wrote a nice article explaining step-by-step how to write
shell code to and to use it in exploits.
DETAILS
"It's not an easy task to find a vulnerable service and find an exploit
for it. It's also not easy to defend against users who might want to
exploit your system, if you are a system administrator. However, writing
an exploit by yourself, to convert a news line from bug tracker into a
working lockpick, is much more difficult. This article is not a guide on
writing exploits, nor an overview of popular vulnerabilities. This is a
step-by-step guide on developing a shellcode, a crucial point of any
exploit software. Hopefully, learning how they work will help
conscientious and respectable developers and system administrators to
understand how malefactors think and to defend their systems against
them..."
Read full article here:
<http://www.linuxdevcenter.com/lpt/a/6590>
http://www.linuxdevcenter.com/lpt/a/6590
ADDITIONAL INFORMATION
The original article can be found at:
<http://www.linuxdevcenter.com/lpt/a/6590>
http://www.linuxdevcenter.com/lpt/a/6590
========================================
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: list-unsubscribe@xxxxxxxxxxxxxx
In order to subscribe to the mailing list, simply forward this email to: list-subscribe@xxxxxxxxxxxxxx
====================
====================
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.
- Prev by Date: [EXPL] phpBazar File Inclusion (Exploit)
- Next by Date: [UNIX] Prodder Arbitrary Command Execution
- Previous by thread: [EXPL] phpBazar File Inclusion (Exploit)
- Next by thread: [UNIX] Prodder Arbitrary Command Execution
- Index(es):
Relevant Pages
|
|
