Browsers send Host Header to inform about the URL client wants to visit. Attackers can temper Host Header to manipulate how the application works. Here is how this attack occurs:
Attacker mak...
Updated May 13, 2020
Version 2.0
Blog Post
This seems to eliminate the vulnerability from port 443 but my scanner is still showing it on port 80. While I could disable binding to port 80, we also use rewrite to redirect from 80 to 443. So I'm guessing the order in which this happens does matter?