After successful completion of the course, students are able to... still to be completed, still to be completed, still to be completed, still to be completed, still to be completed, still to be completed,...

• run time organization of programs
• code injection attacks and defenses
• buffer overflows und stack canaries
• ontrol-flow hijacking und control-flow integrity
• code re-use attacks and defenses
• return-oriented programming und software diversity
• non-control data attacks und data-flow integrity and data randomization
• recent results
• theoretical security of control-flow integrity
• trends in software diversity

To be done.

• Vorlesungsbesuch (incl. Vor- und Nachbereitung): 35h
• Uebungsaufgaben: 30h
• Pruefungsvorbereitung und muendliche Pruefung: 10h

To be done.