Skip to content

Latest commit

 

History

History
100 lines (82 loc) · 6.21 KB

README.md

File metadata and controls

100 lines (82 loc) · 6.21 KB
Raw

Web Security Essentials

This is the workshop material for Web Security Essentials!

Workshop Prerequisites

To have a productive workshop experience, please do the following:

  • Review the Code of Conduct (~5 minutes)
  • Install and setup Zoom on the computer you will be using (~5 minutes)
  • If you are unfamiliar with Zoom, watch Kent C. Dodds's free lesson Use Zoom for KCD Workshops
  • Install Charles
  • Verify your computer has the following installed and available in your PATH (~5 minutes)
    • git (verify by running git --version)
    • NodeJS v8.9.3 or greater (verify by running node --version)
    • npm (verify by running npm --version)
    • curl (verify by running curl --version)
    • If you have trouble with this, learn more about setting your PATH here for windows or mac.
  • Ensure you have sudo (on mac/linux) or run your CLI as an Administrator (Windows).
  • Add the following to your hosts file, located at /etc/hosts (mac/linux) or c:\Windows\System32\Drivers\etc\hosts (windows). You may need sudo or Administrator privileges: 
    127.0.0.1	localhost evil.com
  • Ensure you can successfully run the code (~5 minutes)
    • PLEASE ONLY ATTEMPT TO START THE FIRST EXERCISE. IF YOU JUMP AHEAD, YOU MAY ACCIDENTALLY TRIGGER HSTS AND WE'LL NEED TIME TO UNDO IT
    • Run sudo npm install. This will prompt you for your password, please enter it
    • Go to the first exercise cd exercises/01
    • Run sudo npm start. If sudo npm start fails, try nodemon ./site/index.js
    • open http://localhost.charlesproxy.com and verify you see a login
    • Run sudo npm run start:evil.com. If that fails, try node ./evil.com/index.js
    • Open https://evil.com:666/index.html and verify you see "thanks for visiting!"
  • Optional, but recommended: Read prerequisite learning material (~20 minutes)

Workshop Workflow

The workshop works as a series of exercises located in the exercises directory. We will work our way progressively through the concepts. At any point in time, if you get stuck, you can find the solution by doing git show lesson-<lesson number> (e.g. git show lesson-2) or view the solution directly in github at e.g. https://github.com/mikesherov/web-security-essentials/commit/lesson-2. If you're still stuck, don't worry! We'll move onto the next lesson, and you'll have a fresh copy of the working code to work off of.

All of the required npm dependencies you'll need throughout the workshop are already listed in package.json. You should only have to npm install once at the very beginning. Our time will be spent working through code and concepts, not waiting for dependencies to finish installing :-).

The workshop uses expressjs as the server software, but all of the techniques you'll learn apply to any server software. Try not to worry too much about expressjs specific questions. The goal is to learn how these attacks work and how to generically mitigate them!

At the beginning of each lesson, you'll cd exercise/<exercise-number> and then run sudo npm start to start up the server. Saving changes will automatically restart, thanks to nodemon. For a few lessons, you'll need to start up an attacker website by running sudo npm run start:evil.com in another terminal window to start up the attacker's server.

The workshop is written and tested on a Mac in Chrome. Please use Chrome and a Mac if possible.

Workshop Outline

You will be learning to exploit and mitigate the following security vulnerabilities and attacks:

  1. Man-in-the-Middle
    1. Simulate a Session Hijacking attack
    2. Set up https
    3. Redirect http to https
    4. Set the Secure cookie flag
    5. Set up HSTS
  2. 5 minute break 😅
  3. CSRF
    1. Create an attack
    2. Set the sameSite cookie flag
    3. Add CSRF tokens to forms and fetch
  4. 15 minute break 😅
  5. XSS
    1. Create a cookie stealing attack via inline JS injection
    2. Set the httpOnly cookie flag
    3. Create a body stealing attack via inline JS injection
    4. Set up a "report only" CSP directive
    5. Block inline script execution and eval with CSP
    6. Create a body stealing attack via script injection
    7. Block script injection with CSP src nonces
    8. Create a credential stealing attack via iframe injection
    9. Explicitly allow only needed sources with CSP

FAQ

Q: When running sudo npm start or sudo npm run start:evil.com, I see the following error: EADDRINUSE: another service on your machine is using the current port. A: You already have a process running on port 80, 443, or 666. Most likely, it's from another node process still running from this workshop. For Windows, please follow these instructions. For Mac/linux, you can run: sudo killall node, which will end whatever node processes you currently have running.

License

This material is available for private, non-commercial use under the GPL version 3. Please contact me at [email protected] for permission to use for any other use.