Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with shellcode
Search options answers only
not deleted
user 5411
In computer security, a shellcode is a small piece of code used as the payload in the exploitation of a software vulnerability. It is called "shellcode" because it typically starts a command shell from which the attacker can control the compromised machine, but any piece of code that performs a similar task can be called shellcode.
2
votes
Is my understanding of buffer overflows correct?
Usually, no, buffer overflow exploits is not about overwriting code. But there are definition issues.
A buffer overflow exploit (of the "write" kind) leverages a situation where the target system can …
- 174k
13
votes
Accepted
Stack buffer overflow confusion
Simply put, the complete overflow will look like this:
90 90 90 90 90... 90 shellcode addr addr addr... addr
where shellcode is the actual payload, 90 is the hexadecimal code for the nop opcode, and … Which one is not very important, because the CPU will proceed to execute all subsequent nop opcodes and then reach the shellcode.
The pictures you show are indeed quite confusing. …
- 174k
20
votes
NX bit: does it protect the stack?
The NX bit is a feature of the Memory Management Unit of some CPU (including recent enough x86). It allows to mark each memory page as being "allowed" or "disallowed" for code execution. The MMU is un …
- 174k