Getting FREAK-y with BIG-IP

The other vulnerability, as per the SOL, is with HTTPS monitors, but: 1. Monitors are almost always exclusively used on the private network, isolated from the public. 2. If someone is in position to MITM your monitor traffic, and they go through all of the effort to do so, they'll manage to obtain decrypted - monitor traffic. It is exceedingly rare that someone would have sensitive data in their HTTPS monitors. So they have the export RSA key - but the management plane isn't normally opening connections that could be MITM'd, except for monitors. And if the servers being monitored are patched to not support export RSA ciphers, then the MITM won't work to start with. So patch those servers. There is a mitigation in the SOL (-kRSA), but the user has to decide if it is really necessary.