Scribd Logo
Upload

Welcome to Scribd!

  • ECE 102 – Compilation and Exploits

    Uploaded by

    Brandt Groene
    8 views15 pages
    This document summarizes an ECE 102 lecture on compilation and exploits. It discusses compiling C code with GCC, disassembling object files, common exploits like buffer overflows and stack smashing, and ways to protect against exploits like using strncpy instead of strcpy and specifying the number of bytes copied. It also defines common malware types like viruses, trojan horses, and worms.

    Original Description:

    Notes on assembly

    Original Title

    ECE 102 Notes

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This document summarizes an ECE 102 lecture on compilation and exploits. It discusses compiling C code with GCC, disassembling object files, common exploits like buffer overflows and stack smashing, and ways to protect against exploits like using strncpy instead of strcpy and specifying the number of bytes copied. It also defines common malware types like viruses, trojan horses, and worms.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    8 views15 pages

    ECE 102 – Compilation and Exploits

    Uploaded by

    Brandt Groene
    This document summarizes an ECE 102 lecture on compilation and exploits. It discusses compiling C code with GCC, disassembling object files, common exploits like buffer overflows and stack smashing, and ways to protect against exploits like using strncpy instead of strcpy and specifying the number of bytes copied. It also defines common malware types like viruses, trojan horses, and worms.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 15

    ECE 102 Compilation and

    Exploits
    subtitle: week 7

    Peter Jamieson
    Miami University

    Today
    The machine and C
    Computer engineers
    Who the experts are hackers
    Virus
    Smash the stack

    Compiling
    What happens?

    Gcc options and Object dumps


    gcc S = generate assembly file
    gcc save-temps = keep temp files
    .i = pre_process
    .s = assembly
    .o = object file
    Note ELF at start = Executable and Linkable Format

    objdump -d program.o
    shows the assembly instructions beside the
    machine code

    objdump -d program.exe
    Linker adds some steps

    Other tools
    readelf -h program.exe
    readelf -S program.exe
    Compare what we learned with gdb

    What is?
    A virus
    A trojan horse
    A worm

    What is?
    A virus = program that attaches to exe and
    replicates in other exes unknowingly, but
    program with virus must run
    A trojan horse = looks like legit software but
    you click to run
    A worm = like a virus, but some data transfers
    it and then it replicates

    How do we stop?
    Thoughts?

    The PC smashing the stack


    How big can the password be, and how do we
    implement this in code?

    Details:
    https://www.youtube.com/watch?v=1S0aBV-Waeo

    Smashing the stack


    Buffer overflow
    need to compile gcc with -fno-stack-protector
    gcc -g program.c -fno-stack-protector

    Smash stack
    Almost all computer exploits look for memory
    copies that can be overflowed to hit the return
    address and then run your code
    How can I write code without compiling in this
    exploit?
    Think login

    How do we protect against stack


    smashing?
    We know about smash the stack, how do we
    protect?

    Make sure when memory is copied


    we specify how many bytes
    strcpy
    VERSUS

    strncpy = n specifies how many bytes!!!

    Challenge
    Given PROGRAM_26
    Add a printf statement
    Answer the following

    How much bigger in bytes is the program?


    How big is the printf functionality?
    Where is printf located in memory for this program?
    What code is run before main?

    You might also like