Closed Ph4k3r closed 6 years ago
This might help: https://www.cyberark.com/threat-research-blog/red-team-insights-https-domain-fronting-google-hosts-using-cobalt-strike/
If I had to guess, it looks like your Host
setting is still using port 80, which might be a problem (doubly so if your listening serve is running on 80). I don't have that much experience with fronting, though, so take that with a huge grain of salt.
@DakotaNelson Hi there, I checked the link you gave, but seems not solving my problem. How about this: which EXACTLY option will set to Host and Which should be set to headers?
I think I should set Host to a0.awsstatic.com
And set Headers to my xxxx.cloudfront.net
Hope empire could progress on this quickly.
@Ph4k3r This post may help also: https://www.xorrior.com/Empire-Domain-Fronting/. You need to set the Host header within the profile as shown in the blog post. Also consider that modifying the host header does not work in Win7/ .NET v2|3. Domain . I would also review #971 and #533.
Not related but may be useful for future reference: Google disables “domain fronting” capability
Empire Version
dev
OS Information (Linux flavor, Python version)
Kali 64
Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.
HTTP domain fronting is working, with the following configuration:
But when it comes to HTTPS, it's just not working:
Screenshot of error, embedded text output, or Pastebin link to the error
A lot of retransmissions on wireshark, and If i exchange the "Headers" field with "Host" fields(for HTTPS domain fronting), it's not fronting.
Any additional information
There're no blogs about 2.5 domain fronting with SSL on the webs.... So sad!