Content handlers include the mod_php, mod_ruid2, mod_cgi, and mod_suphp Apache modules. The Bluehost patch does not affect requests that the system processes with application content handlers. However, the Bluehost patch only affects requests for static files such as. The patch helps to ensure that the system can only access files that the domain's owner owns. The Bluehost patch modifies Apache and APR so that Apache cannot access certain files. The Bluehost patch's goal is to improve Apache's ability to detect a race condition. This patch can slow the performance of high-traffic servers and is not compatible with Mailman or CGI Center applications. We provide this patch with EasyApache 4, but the protection is not as reliable as kernel or file system level solutions. This is an Apache-level patch and considered a last-resort defense. This is what the cPanel documentation says:ĬPanel & WHM only provides the -provided patch with some modifications. It seems that perhaps cPanel does provide the Bluehost Apache now, but it isn't listed under EA4, like it was with EA3. Symlink Race Condition Protection - EasyApache 4 - cPanel Documentation I think I just found the solution to my question: The Bluehost patch modifies the source code to Apache and then when Apache is compiled, it provides protection. WHMxtra has been completely removed because I didn't like it, however, a quick google search seems to show it didn't come from them. I simply refer to it as the bluehost patch, because Bluehost was the company who created the patch. When EA3 provided Symlink Protection, they were using the patch provided by Bluehost. They said they do not do that stuff, and if they ever had to, they would contact the customer first. I did contact buycpanel and they did not provide this patch, nor did they install it. When I say bluehost, I'm talking about the Apache 2.4 patch that prevents the symlink race condition. Please post additional info as you progress with the problem solving of this, as a help to others on such a complex issue. Unfortunately i can not offer much more advice than this. This is just my opinion on how to approach the situation starting out. Solution: Look in the admin controls and see if you can uninstall and/or secure afterwards.

WHMxtra: If you have this system it may have installed Bluehost. Your current host: If they installed Bluehost it is probably to support their server setups as some type of workaround. Solution: Contact support and ask if, why, how to remove and how to secure after removing Bluehost. I suspect they did it because:īuycpanel: If they installed Bluehost it is probably to support and/or allow something they install with cPanel. Your host or buycpanel installed Bluehost as it is a plugin.

Bluehost cpanel login