file

Suche

Unten sind die Ergebnisse Ihrer Suche gelistet.

Volltextergebnisse:

Shellcode Injection Part 1 @en:it-security:blog
10 Treffer, Zuletzt geändert:
should be in C format | | > shell.c | Save to the file shell.c | <code bash> msfvenom -p windows/shell_... tes. We take this from the ''msfvenom'' output. <file cpp local-process-injection.cpp> #include <stdio.... ad, size); ((void(*)())code)(); return(0); } </file> \\ \\ ==== Analyse shellcode ==== After compili... s> python3 jigsaw.py shell.raw </code> and get a file with C++ code. <code c++> unsigned char jigsaw[5
Buffer Overflow im 64-Bit Stack - Teil 3 @it-security:blog
8 Treffer, Zuletzt geändert:
/nosoc-bof/tree/main/part-3|Github]] verfügbar. <file c bof-part3.c> /* Code https://blog.techorganic.c... setbuf(stdout, 0); vuln(); return 0; } </file> \\ \\ ===== Debug ===== {{page>vorlagen:attent... s ein erstes Exploit, um ''write()'' zu leaken. <file python buf3-stage1.py> #!/usr/bin/env python fro... eaked write address: {}".format(hex(got_leak))) </file> Wir führen das Ganze aus und erhalten folgende
Buffer overflow in the 64-bit stack - Part 3 @en:it-security:blog
8 Treffer, Zuletzt geändert:
h>psycore8/nosoc-bof/tree/main/part-3|Github]]. <file c bof-part3.c> /* Code https://blog.techorganic.c... setbuf(stdout, 0); vuln(); return 0; } </file> \\ \\ ===== Debug ===== {{page>en:vorlagen:att... s write a first exploit to ''write()'' to leak. <file python buf3-stage1.py> #!/usr/bin/env python fro... eaked write address: {}".format(hex(got_leak))) </file> We run the whole thing and get the following ou
Shellcode Injection Teil 1 @it-security:blog
4 Treffer, Zuletzt geändert:
. Diese entnehmen wir der ''msfvenom'' Ausgabe. <file cpp local-process-injection.cpp> #include <stdio.... ad, size); ((void(*)())code)(); return(0); } </file> \\ \\ ==== Shellcode analysieren ==== Nach dem ... calc_payload[position] = jigsaw[idx]; } </code> <file c++ Inject.cpp> #include <stdio.h> #include <Wind... size); ((void(*)())code)(); return(0); } </file> Jigsaw allein reicht an dieser Stelle jedoch ni
Buffer overflow in the 64-bit stack - Part 2 @en:it-security:blog
4 Treffer, Zuletzt geändert:
per and display the gadgets <code bash> ropper --file bof-part2 ... 0x000000000040116a: pop rdi; ret; .... ll need 2 offsets for the exploit. So we load our file into the debugger and start it: <code bash> gdb-... === Now we run our Python exploit and create the file in.txt. <code bash>python2 buffer.py</code> \\ \\ ==== Set authorisations ==== Our file still needs the appropriate root permissions. <c
IT Security Cheat Sheets @it-security
1 Treffer, Zuletzt geändert:
tps://gist.github.com/Stolas/c67b0d6ce1de78869764#file-gdb-cheatsheet-L65|Github]] | ^ ::: | Metasploit
Buffer Overflow im 64-Bit Stack - Teil 2 @it-security:blog
1 Treffer, Zuletzt geändert:
en uns die Gadgets anzeigen <code bash> ropper --file bof-part2 ... 0x000000000040116a: pop rdi; ret; .
Buffer overflow in the 64-bit stack - part 1 @en:it-security:blog
1 Treffer, Zuletzt geändert:
==== First we set root rights to the vulnerable file and start it((https://blog.techorganic.com/2015/0
Privilege escalation: Windows admin thanks to Linux @en:it-security:blog
1 Treffer, Zuletzt geändert:
]] After the download you have to port the image file to a bootable USB stick or DVD. To ensure that th