From 663090440d00214ffdbccd4509232bffae8dc188 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=94=D0=B0=D0=BD=D0=B8=D0=B8=D0=BB=20=D0=9D=D0=B8=D0=BA?= =?UTF-8?q?=D0=BE=D0=BB=D0=B0=D0=B5=D0=B2?= Date: Tue, 10 Dec 2019 15:46:18 +0400 Subject: [PATCH] Update CSRF.md --- Methodology/CSRF.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/Methodology/CSRF.md b/Methodology/CSRF.md index 5546a79..02dee47 100644 --- a/Methodology/CSRF.md +++ b/Methodology/CSRF.md @@ -1 +1,6 @@ -### CSRF +# CSRF + + - Check if the framework used by the app uses any kind of CSRF protection built in. + - Remember that "Any application that accepts HTTP requests from an authenticated user without having some control to verify that the HTTP request is unique to the user's session.". Try to find requests that doesn't send any cookies or params that look like a csrf token. + - Check how and by what endpoint the token is being generated. + - Check if the token is statefull (The token is stored somewere on the server) or is stateless (the token is validated using some kind of algorithm).