CirrusHello,
I've been testing session hijacking lately.
Here is my setting
I have found that when I change SESSION or TS01340bfb individually, F5 blocks it.
However, when I change both, it doesn't block it and I can run session hijacking successfully.
Why is this happening ... ?
Any help is appreciate.
MVPBetter see this as I do not see feature cookie only the main F5 cookie https://my.f5.com/manage/s/article/K6850
https://my.f5.com/manage/s/article/K95345460
Maybe enable session tracking and see that the SESSION cookie is enforced.
The ASM Feature cookies
The ASM Feature cookies are set for client requests when one or more BIG-IP ASM features are activated or enabled, such as the following policy features:
MVPDid you test it? Also you can add session tracking by Device ID that is generated by the bot defense and this way if someone steals the 2 cookies they can't use them.
Still when you mentioned that when changing the 2 cookies F5 does not block you, well the idea is to someone not using real cookies that are not their own, so when you randomly changed the two cookies they are no longer a real TS or real sesson cookie that can be used.
MVPFunny, I came across the same issue recently in a customer scenario. Nikoolayy1 is correct.
Here are my 5 cents.
1. Steal one cookie > ASM will block.
2. Steal both cookies > ASM won't block this, Session Hijacking is possible.
3. Enable a Bot Defense profile for this VS and configure it to create a Device ID.
4. Configure the following in the learning and blocking settings:
This way hijacking the session by stealing both cookies will fail.
KR
Daniel
MVPAlso APM can be added so that each device to be checked if it is corporate https://techdocs.f5.com/kb/en-us/products/big-ip_asm/manuals/product/asm-implementations-13-0-0/15.html , using the APM checks. Even if someone steals even the APM cookie after some time their device will be checked.