liveBook · Manning

Buffer overflow

A buffer overflow is a memory-safety flaw in which software reads or writes beyond the bounds of a buffer.

How 3 Manning books explain it

Tech Startup Toolkit

A buffer overflow is a software flaw in which data written to a memory buffer exceeds its bounds and overwrites adjacent memory.

How it is used
Frames stopping buffer overflow as a minimum viable product priority for a cybersecurity offering.
How deep it goes
Mentions buffer overflow only as a common attack and defers its mechanics and mitigation.
Examples
Uses NXP’s assessment that stopping buffer overflow would differentiate Dover’s product.
What you can do after
Evaluate/understand it as a candidate MVP security capability and market differentiator.

Read how Tech Startup Toolkit explains buffer overflow →

Fundamentals of Cybersecurity

A buffer overflow is a condition in which input exceeds a buffer's capacity and overwrites adjacent memory.

How it is used
Frames buffer overflow as an application vulnerability caused by input exceeding reserved storage.
How deep it goes
Explains the form analogy, memory overwrite mechanism, and possible effects without detailing exploit steps.
Examples
Uses a 10-letter form field and a 20-letter name to illustrate data spilling into adjacent space.
What you can do after
Understand how oversized input can overwrite memory and disrupt a program.

Read how Fundamentals of Cybersecurity explains buffer overflow →

Hacking Cryptography

A buffer overwrite occurs when software writes beyond a buffer's valid bounds and changes adjacent memory.

How it is used
Explains buffer bounds as a practical security requirement for cryptographic and network-server implementations.
How deep it goes
Traces unchecked input through vulnerable C code and defenses, but stops short of a complete exploit.
Examples
Uses HTTP input, server memory, unsafe C functions, Heartbleed, and an OpenSSL heartbeat-processing listing.
What you can do after
Diagnose/debug with it by checking lengths, replacing unsafe functions, and identifying reads or writes beyond allocated buffers.

Read how Hacking Cryptography explains buffer overflow →

Also covered in

What to know first

Related concepts

Questions about buffer overflow

What is buffer overflow?

A buffer overflow is a memory-safety flaw in which software reads or writes beyond the bounds of a buffer.

Which Manning books explain buffer overflow?

Tech Startup Toolkit, Fundamentals of Cybersecurity and Hacking Cryptography.

What should I know before learning buffer overflow?

Manning books that teach buffer overflow usually introduce C11, JavaScript and return-oriented programming first.

What is the difference between buffer overflow and buffer overread?

A buffer overflow is a memory-safety flaw in which software reads or writes beyond the bounds of a buffer. A buffer overread is a software flaw in which code reads beyond the valid or intended bounds of a memory buffer.

What is buffer overflow a kind of?

Buffer overflow is a kind of vulnerability. A vulnerability is a weakness or condition that makes a system, person, or group susceptible to exploitation, compromise, or other harm.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.