[REVS] Exploiting Uninitialized Data Bugs

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

- - - - - - - - -



Exploiting Uninitialized Data Bugs
------------------------------------------------------------------------


SUMMARY

The following whitepaper presented here explains several ways to
exploiting uninitialized variable bugs.

DETAILS

Introduction:
If you have even read just a handful of man pages before, then you will
know all too well that a lot of functions can have undefined behavior .
This article attempts to define what exactly undefined behavior refers to
when dealing with uninitialized variables, and will give examples of how
this could be abused by attackers to control the execution flow of an
application. All the examples have been tested and found working on Ubuntu
Linux. It is hoped that the reader will extend on the information
provided, and look at similar conditions in glibc functions, kernel code,
and threaded applications.

Requisites:
All of the example code is written in the C programming language and x86
assembler. As a reader
you should be comfortable in these languages, as well as comfortable in
navigating around a
disassembler and man pages.

The whitepaper and example code can be found at:
<http://www.felinemenace.org/~mercy/papers/UBehavior/UBehavior.zip>
http://www.felinemenace.org/~mercy/papers/UBehavior/UBehavior.zip


ADDITIONAL INFORMATION

The information has been provided by <mailto:mercy@xxxxxxxxxxxxxxxx>
mercy.



========================================


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.

Relevant Pages