We were previously vulnerable to cross-site request forgery: someone giving us a link that ran an action from somewhere else. To fix this, we can tie a token which is sent along with all our actions to a session. That way, an attacker won't know the correct token to run an action on behalf of a user
menu
+210
-4
menu/Cargo.lock
+2
menu/Cargo.toml
+1
menu/src/html/create.html
+1
-1
menu/src/html/create/conflict.html
+1
-1
menu/src/html/create/success.html
+89
-9
menu/src/main.rs
History
6 rounds
0 comments
1 commit
expand
collapse
We were previously vulnerable to cross-site request forgery: someone
giving us a link that ran an action from somewhere else. To fix this, we
can tie a token which is sent along with all our actions to a session.
That way, an attacker won't know the correct token to run an action on
behalf of a user
expand 0 comments
1 commit
expand
collapse
We were previously vulnerable to cross-site request forgery: someone
giving us a link that ran an action from somewhere else. To fix this, we
can tie a token which is sent along with all our actions to a session.
That way, an attacker won't know the correct token to run an action on
behalf of a user
expand 0 comments
1 commit
expand
collapse
We were previously vulnerable to cross-site request forgery: someone
giving us a link that ran an action from somewhere else. To fix this, we
can tie a token which is sent along with all our actions to a session.
That way, an attacker won't know the correct token to run an action on
behalf of a user
expand 0 comments
1 commit
expand
collapse
We were previously vulnerable to cross-site request forgery: someone
giving us a link that ran an action from somewhere else. To fix this, we
can tie a token which is sent along with all our actions to a session.
That way, an attacker won't know the correct token to run an action on
behalf of a user
expand 0 comments
1 commit
expand
collapse
We were previously vulnerable to cross-site request forgery: someone
giving us a link that ran an action from somewhere else. To fix this, we
can tie a token which is sent along with all our actions to a session.
That way, an attacker won't know the correct token to run an action on
behalf of a user
expand 0 comments
1 commit
expand
collapse
We were previously vulnerable to cross-site request forgery: someone
giving us a link that ran an action from somewhere else. To fix this, we
can tie a token which is sent along with all our actions to a session.
That way, an attacker won't know the correct token to run an action on
behalf of a user