Does anyone know what actual version of lighttpd the sw-cp-server is based on? The version output it spits out always says 1.0.0 while the Plesk rpm will be 1.0.6 or 1.0.7 (plesk 9 vs 10). However, I can't imagine those are the actual versions of lighttpd because there hasn't been a 1.0.x release of that in 7+ years from what I can tell.
The reason I ask is because the current Plesk lighttpd-based web server in both version 9 and 10 (haven't tried 11 yet) is vulnerable to SSL renegotiation attacks CVE CVE-2011-1473 (http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-1473) and the SSL BEAST attack (https://community.qualys.com/blogs/securitylabs/2011/10/17/mitigating-the-beast-attack-on-tls). Several PCI scanning companies are starting to fail sites over either, or both, of these alerts due to port 8443 having the vulnerabilities.
lighttpd versions 1.4.30 and newer from late 2011 resolve this issue:
http://redmine.lighttpd.net/versions/28
ssl: disable client initiated renegotiations
ssl: support mitigating BEAST attack
Has Parallels customized lighttpd in any way beyond the config files or could we potentially drop a copy of 1.4.31 on top of the sw-cp-server binary to close the vulnerability?
The reason I ask is because the current Plesk lighttpd-based web server in both version 9 and 10 (haven't tried 11 yet) is vulnerable to SSL renegotiation attacks CVE CVE-2011-1473 (http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-1473) and the SSL BEAST attack (https://community.qualys.com/blogs/securitylabs/2011/10/17/mitigating-the-beast-attack-on-tls). Several PCI scanning companies are starting to fail sites over either, or both, of these alerts due to port 8443 having the vulnerabilities.
lighttpd versions 1.4.30 and newer from late 2011 resolve this issue:
http://redmine.lighttpd.net/versions/28
ssl: disable client initiated renegotiations
ssl: support mitigating BEAST attack
Has Parallels customized lighttpd in any way beyond the config files or could we potentially drop a copy of 1.4.31 on top of the sw-cp-server binary to close the vulnerability?