- Reviewed C coding
- watched this video to understand pointers
- Watched videos on buffer overflow attacks to understand what they are / how they work
- Researched how to access memory of other programs in C
- Found this, nothing really useful
- Tested out doing a buffer overflow attack to better understand them
- Successfully did a buffer overflow attack
- Read this for more info on memory addresses
- started working on the part of project that shows the address pointers for all the functions in a file
- Similar to this
- made function that shows address pointers by running terminal comands
- might change it later to not use terminal commands
- found this research for if I want to change it later
- https://www.geeksforgeeks.org/address-function-c-cpp/
- https://stackoverflow.com/questions/21260735/how-to-invoke-function-from-external-c-file-in-c
- might change it later to not use terminal commands
- was absent
- started research on override-return function
- mainly just ran buffer overflow attacks to get used to overriding the return manually
- finalized the function finding part of our project
- made draft of override-return, need to test it more.
- added override-return and help functions.
- worked on presentation with Salaj
- made drafts of homework files for attacking
- watched videos to gain general knowledge on buffer overflows
- was absent (AP Exam)
- was absent (sick)
- worked on PRESENTATION.md
- read/watched these resources
- https://www.youtube.com/watch?v=YVlTDPhTA9U
- https://www.youtube.com/watch?v=hJ8IwyhqzD4
- https://www.youtube.com/watch?v=fjMrDDj47E8
- https://www.youtube.com/watch?v=TuI2HyG8-iI
- https://www.youtube.com/watch?v=hJ8IwyhqzD4&t=8s
- https://www.rapid7.com/blog/post/2019/02/19/stack-based-buffer-overflow-attacks-what-you-need-to-know/
- https://www.youtube.com/watch?v=eg0gULifHFI
- got 32 bit buffer overflow attack to work
- read this article: https://medium.com/@buff3r/basic-buffer-overflow-on-64-bit-architecture-3fb74bab3558
- outlined features that our app will have
- created template for tool src files
- researched how ptrace works
- created basic program that can view the eip of a process
- created template for tool's src files
- started work on the finding offset part of our tool
- created a projected API in README.md
- tested out ptrace and tried to figure out how it works
- added on to PRESENTATION.md
- watched https://www.youtube.com/watch?v=SajNnjeHOWI to understand how to approach finding offset (will use pattern generation)
- continued work on accessing return address of another program using ptrace
- researched ptrace more (its very complicated)
- researched pattern matching
- made the makefile
- integrated all the different functions
- worked on the presentation and homework files
- finished code obfuscation (realized that PTRACE wont work so went with terminal command and pattern generation option)