Bad CSRF Token when attempting to whitelist hashes from API

YAlhazmi — Sat, 23 Jan 2021 10:49:42 GMT

Hey everyone,

We are trying to whitelist a bulk of hashes using the Cortex XDR API (because the UI isn't working, we have an open case with support). The request always return the same error:

400 Bad CSRF Token

Access is denied. This server can not verify that your cross-site request forgery token belongs to your login session. Either you supplied the wrong cross-site request forgery token or your session no longer exists. This may be due to session timeout or because browser is not supplying the credentials required, as can happen when the browser has cookies turned off.

check_csrf_token(): Invalid token

This error ONLY shows up when we attempt to whitelist hashes. We can retrieve incidents and alerts using the same code (and hence same API key and ID) without any problem. The image below shows that it has key should be able to update the allow list.

The url: "https://api-{domain}/public_api/v1/hash_exceptions/allow_list/"

Any ideas are appreciated!

P.S. This is the error from the UI

Re: Bad CSRF Token when attempting to whitelist hashes from API

kreeves — Wed, 24 Feb 2021 16:21:09 GMT

I see the same behaviour

Re: Bad CSRF Token when attempting to whitelist hashes from API

kreeves — Fri, 26 Feb 2021 19:44:51 GMT

This is a documentation problem. The correct path is

/public_api/v1/hash_exceptions/allowlist/

NOT

/public_api/v1/hash_exceptions/allow_list/

topic Bad CSRF Token when attempting to whitelist hashes from API in Automation/API Discussions

Bad CSRF Token when attempting to whitelist hashes from API

Re: Bad CSRF Token when attempting to whitelist hashes from API

Re: Bad CSRF Token when attempting to whitelist hashes from API