Forum Discussion
cjunior_138458
Altostratus
May 08, 2017A way to mitigate CVE-2017-8295
Hello experts,
I may be wrong in my approach, but I'm trying to mitigate CVE-2017-8295 by forcing the request to a know fixed host name, (e.g. ).
So when another requested host reach my virtual serve...
nathe
Cirrocumulus
May 08, 2017cjunior,
I dont believe this Host Header configuration object works as you believe it should, rather it is a way of telling certain protections of internal/external host names.
Anyway, another option is to create a custom attack signature perhaps? You would want to use the headercontent value to not match the actual host address.
Something like this should work:
headercontent:"Host"; nocase; re2:!"/www.example.com/"; nocase;
See if this helps,
N
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects