The RC4 algorithm, as used in the TLS protocol and SSL protocol, does not properly combine state data with key data during the initialization phase, which makes it easier for remote attackers to conduct plaintext-recovery attacks against the initial bytes of a stream by sniffing network traffic that occasionally relies on keys affected by the Invariance Weakness, and then using a brute-force approach involving LSB values, aka the "Bar Mitzvah" issue
EHealth - all versions
This issue is with the openSSL protocol, so it cannot be fixed by CA.
1. As a workaround, the customer can modify $NH_HOME/web/httpd/httpd.tpl file, so it should look like the following:
# Custom Protect Section
SSLProtocol -ALL +TLSv1.2 +TLSv1.1
# End Custom Protect Section
Then the customer should regenerate httpd.conf using nhWebProtocol command.
E.g. nhWebProtocol -mode https -port 443 -hostname `hostname` -fips
If you need to use FIPS protocol in your environment, run:
nhWebProtocol -fips <whatever other arguments you need>
Which enables FIPS mode for apache httpd server and disables all non-secure ciphers (eHealth 6.3.2.07+).