browser-csrf v1.1.0

browser-csrf :lock:

inject csrf tokens into your browser's network calls.

what

injects a token on each:

• xhr request
• fetch request
• form submission

usage

// example
var BrowserCSRF = require('browser-csrf')
var bcsrf = new BrowserCSRF({ token: '<your-csrf-token>' })
bcsrf.inject()

this is a fairly simple example. see the API docs for more.

api

See the official API Docs.

why

CSRF attacks are real. Using an authorization token on each request (such as a CSRF token) helps prevent unauthorization command execution. Using cookies to store auth tokens generally works, but leaves your app vulnerable to malicious social engineering. Malicious actors can lead your users to make network calls against your server using an entirely different website, via HTML forms or cross-origin javascript XHRs, exploiting the fact that your cookies will be passed along, even outside the context your website/domain!

how

how we do this is controversial! we override the XMLHttpRequest.prototype.send method, add a header, & reproxy through to the original method. if you are not comfortable with this, this module isn't for you!

example exploit

See the exploit/ directory for an easy to run, easy to understand example of CSRF.

here's how you can use the demo:

• launch both servers, node exploit/<malicious/vulnerable>/src/index.js
• open a browser to localhost:7777
  • log into the fake bank using the displayed credentials
  • simulate some fund transfers (the ui makes this clear how to do, hopefully :))
  • observe the exploit link at the bottom of the page. click it
    • this link opens a website from the malicious server, and makes your browser execute a command against the vulnerable server on your behalf, unbeknownst to you! this is the very essence of a CSRF!

hopefully you can see that another site's ability to issue a command on a completely different site using an existing authenticated session is a big deal. so, how can we fix it? OWASP has some great documentation on how the attack vectors work. they also provide some basic mechanisms on how to thwart the attack vector from the browser. however, the browser solutions they provide are not very robust for modern native webapps. this browser-csrf fills that gap.

what we will do now is tell our vulnerable server to sniff for CSRF tokens.

• kill the current vulnerable server
• reboot the vulnerable server as such, CSRF_PROTECTION=true node exploit/vulnerable/src/index.js
  • re-navigate to localhost:7777
  • on login, the server provides a CSRF token
  • our browser code, post-login, sets up browser-csrf to make sure each network request gets the token injected into request headers
  • our server will now sniff for CSRF tokens on each request that requires authentication
• repeat the above banking processes
  • observe fund transfers work fine!
  • observe the CSRF attack thwarted from the malicious site!