Suche
Unten sind die Ergebnisse Ihrer Suche gelistet.
Volltextergebnisse:
- Reset the registry at an earlier point in time @en:windows
- thing at this point is that we get access to the file system. ===== Rename and save the old registry =... \Windows\system32\config and rename the following files: - SAM - SECURITY - software - default ... alled Snapshot. This is exactly where we find the files we need: - _REGISTRY_USER_.DEFAULT - _REGIS... restart. If the problem still persists, the process must be repeated with slightly older registry files.
- Obfuscation: polymorphic in-memory decoder @en:it-security:blog
- ep: - We extract the actual shellcode from the file ''%%calc.o%%'' and save it in ''%%calc.raw%%'' (f... ur code and prepare it for our ''%%Inject.cpp%%'' file: <code python> python shencode.py output -f xor-... xor-decoder.stub -fb 60 -lb 329 [*] try to open file [+] reading xor-decoder.o successful! [*] cutting... key 63 python shencode.py create --xor-stub --xor-filename xor.out --xor-outputfile stub.raw --xor-key 6
- Obfuscation: Disguise shellcode as UUIDs @en:it-security:blog
- something like this: <code cpp> [*] try to open file [+] reading 240906.001 successful! [*] try to gen... the victim system. After the copying process, the file is not recognised. We scan it once manually with ... ooks good. ==== Execute ==== We now execute the file and wait for the result. Unfortunately, nothing ... ==== The UUID obfuscation works and protects the file when accessing the hard drive. After execution, m
- Privilege escalation: Windows admin thanks to Linux @en:it-security:blog
- ]] After the download you have to port the image file to a bootable USB stick or DVD. To ensure that th
- Buffer overflow in the 64-bit stack - Part 2 @en:it-security:blog
- 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
- Buffer overflow in the 64-bit stack - Part 3 @en:it-security:blog
- 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... # POP Argumente buf += p64(constants.STDOUT_FILENO) # stdout buf += p64(bin.got[b'write'])
- Shellcode Injection Part 4 @en:it-security:blog
- ode> <callout type="info" icon="true"> Opens the file ''windir\syswow64\kernel32.dll'' in PEView. This ... > Then it is worth taking a look at the compiled file: <code> objdump -d calc-unsanitized.o </code> {... .o -s c </code> The command provides us with the file in C format syntax. We know that our shellcode st