The Web Security Seminar
For registration, please apply for this seminar through the central seminar assignment system.
The Web Security Seminar will teach students to present, analyze, discuss, and summarize papers in different areas of Web security. The seminar combines a reading group with (almost) weekly meetings and a regular seminar, where students will write a seminar paper.
Each student will get a topic assigned, consisting of a lead and a follow-up paper. The student will present the follow-up paper in a 20-minute presentation followed by a 10-minute Q&A. Afterwards we will all discuss the lead paper as a reading group. All students must read the lead paper and, before each session, must submit a summary with strengths and weaknesses.
Finally, each student will write a seminar paper on the topic assigned to them, for which the two papers serve as the starting point.
- Kickoff on Monday, 30.10.2023, 10:15-12:00, CISPA main building, room 0.02
- (Semi) Regular seminar sessions on Mondays. First session is on Monday, 13.11.2023, 10:15-12:00
- Each Sunday at 23:59 before each session, submit the paper summary (one page max) with discussion points: three items for the strengths, three items for the weaknesses, and future work
- Optional feedback round before your session (arrange exact time with your supervisor)
- Attendance in all meetings and submission of summary and discussion points for each topic is mandatory. For exceptional cases, contact the teaching staff.
Note that we will not offer a hybrid solution. We plan to have in-person meetings as long as possible and switch to fully online if the need arises.
Seminar Paper Details
We will cover the different types of seminar paper during the kickoff session.
All seminar papers are due on (see below). Based on your submission, you will receive feedback within one week and have until (see below) to improve your paper. The paper grading will be on the final version. Note that the first submission must already be sufficient to pass. If you submit a half-baked version of the paper, you will likely fail the course.
Each paper must use the provided template. It must not be longer than 8 pages, not counting references and appendices. Note that appendices are not meant to provide information that is absolutely necessary to understand the paper, but rather to provide auxiliary material. Papers can be shorter, but in general the provided page limit is a good indicator of how long a paper should be.
Schedule, List of Topics, and Papers
|Date||Time||Content||Tutor||Main paper (discussed)||Follow-up papers (presented)|
Session 3: Prototype pollution (Nicolas E.)
|Cris||Probe the Proto: Measuring Client-Side Prototype Pollution Vulnerabilities of One Million Real-world Websites|
Session 4: User Browsing Behavior vs. Top Lists (Aniketh)
|A World Wide View of Browsing the World Wide Web|
Session 5: Reproducibility in Web Measurements (Philip)
|Florian||How the Web Tangled Itself: Uncovering the History of Client-Side Web (In)Security|
Session 6: Software Supply Chain Security (Nicolas D.)
|Cris||Towards Measuring Supply Chain Attacks on Package Managers for Interpreted Languages|
Session 7: All Your Secrets Cross Boundaries: Exploring the Risks of Cross-Site Information Leaks (Vedant)
|Jannis||The Leaky Web: Automated Discovery of Cross-Site Information Leaks in Browsers and the Web|
|Cris||Everything Old is New Again: Binary Security of WebAssembly|
Session 9: Web Application Scanners (Prerak)
|Alex||Toss a Fault to Your Witcher: Applying Grey-box Coverage-Guided Mutational Fuzzing to Detect SQL and Command Injection Vulnerabilities|
Session 10: Beyond Malicious Extensions: How can Extensions put User Security & Privacy at Risk? (Meenakshi)
|Aurore||DoubleX: Statically Detecting Vulnerable Data Flows in Browser Extensions at Scale||Detection of Inconsistencies in Privacy Practices of Browser Extensions|