LinuxFocus.org: Avoiding security holes: memory, stack and functions, shellcode

Written By
FR
Frédéric Raynal
Apr 16, 2001

“In our previous article we analyzed the simplest security
holes, the ones based on external command execution. This article
and the next one show a widespread type of attack, the buffer
overflow. First we will study the memory structure of a running
application, and then we’ll write a minimal piece of code allowing
to start a shell (shellcode).”

“Let’s assume a program is an instruction set, expressed in
machine code (regardless of the language used to write it) that we
commonly call a binary. When first compiled to get the binary file,
the program source held variables, constants and instructions. This
section presents the memory layout of the different parts of the
binary.”

“To understand what goes on while executing a binary, let’s have
a look at the memory organization. It relies on different
areas…”


Complete Story

FR

Frédéric Raynal

Linux Today Logo

LinuxToday is a trusted, contributor-driven news resource supporting all types of Linux users. Our thriving international community engages with us through social media and frequent content contributions aimed at solving problems ranging from personal computing to enterprise-level IT operations. LinuxToday serves as a home for a community that struggles to find comparable information elsewhere on the web.

Property of TechnologyAdvice. © 2026 TechnologyAdvice. All Rights Reserved

Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.