Re:WordPress 4.8.1 still vulnerable to Host Header Attack
by kels on Friday September 15, 2017 @12:19PM
(#15258337)
I get where WordPress is coming from by not fixing this issue since it's an Apache thing. But since Apache's default value causes this to happen I think the framework should try to protect its users. The normal user that had their WordPress installed using an application installer on a shared host isn't going to know about this issue.
[ Parent
| on HN ]
Re:WordPress 4.8.1 still vulnerable to Host Header Attack
by KekDemaga on Friday September 15, 2017 @01:10PM
(#15258821)
As mentioned in a previous discussion by calibas, PHP.net has this disclaimer:
"Note: Under Apache 2, you must set UseCanonicalName = On and ServerName. Otherwise, this value reflects the hostname supplied by the client, which can be spoofed. It is not safe to rely on this value in security-dependent contexts."
So it seems to be clearly a Word Press issue.
Re:WordPress 4.8.1 still vulnerable to Host Header Attack
by tombrossman on Friday September 15, 2017 @02:15PM
(#15259361)
With Nginx I've always used this for the first server block to defeat host header attacks, taken from the h5bp boilerplate server configs[0]:
server {
listen 80 default_server;
return 444;
}
Is something like this necessary for Apache as well? If yes, what are others using? (ignoring the non-standard but effective 444 return code)
Re:WordPress 4.8.1 still vulnerable to Host Header Attack
by wolfgang42 on Friday September 15, 2017 @12:32PM
(#15258441)
Fortunately, shared hosts aren't likely to be vulnerable to this attack: in that case, the Host header will be used to identify which shared site to run, so if an attacker changes it they'll get a different site. This vulnerability is only a problem if WordPress is installed as the default site (or has a dedicated IP address), in which case unknown values of the Host header will be passed directly to it.
Re:WordPress 4.8.1 still vulnerable to Host Header Attack
by TazeTSchnitzel on Friday September 15, 2017 @02:45PM
(#15259618)
A given server can effectively have any hostname because of Host:, and that might even be desirable, so Apache's behaviour doesn't seem reasonable.