[REVS] Real Life Vuln-Dev Process of a Win32 Stack Buffer Overflow
From: SecuriTeam (support_at_securiteam.com)
To: firstname.lastname@example.org Date: 15 Sep 2004 10:22:41 +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.
- - - - - - - - -
Real Life Vuln-Dev Process of a Win32 Stack Buffer Overflow
Sergio Alvarez has written a paper on how the process of vulnerability
development works. Sergio focuses on the whole process from discovering
vulnerability through the creation of a proof of concept up to the point
where you write a working exploit code.
Introduction (from the paper):
Many times Sergio has been asked for writing a paper about how to code an
exploit for win32, for two reasons, first because there are many papers
about exploitation on *nix, but few about how to exploit on win32 world,
and second because papers about win32 exploitation get very difficult to
be understood by people without a good understanding of ASM, C languages.
So Sergio thought that the best way to do something clear he had to write
something as simple as possible, without leaving nothing to guess by the
readers. Well this is what Sergio think is the easiest that he could do.
And explaining the hole process of finding, debugging and exploiting a
black box application. For this purpose Sergio has chosen 'War-FTPd v1.65'
a known stack b0f bugged software, which is gonna be used in this
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@example.com
In order to subscribe to the mailing list, simply forward this email to: firstname.lastname@example.org
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.