Skip to content

Fix #rop reference #280

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kbeyls merged 1 commit into from
Nov 20, 2025
Merged

Fix #rop reference #280

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion book.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -342,7 +342,7 @@ Some examples of how the attacker may use the obtained primitives:

* Leak information, such as pointers to specific data structures or code,
or the stack pointer.
* Overwrite the stack contents, e.g. to perform a [ROP attack](#rop).
* Overwrite the stack contents, e.g. to perform a [ROP attack](#return-oriented-programming).
* Overwrite non-control data, e.g. authorization state. Sometimes this
step is sufficient to achieve the attacker's goal, bypassing the need for
arbitrary code execution.
Expand Down