I've just been told the following. Stingray Traffic Manager (software) is not vulnerable in any respect to this bug as we do not use OpenSSL for the SSL/TLS protocol (we have our own implementation). Stingray Traffic Manager (virtual and hardware appliances): includes a vulnerable copy of the OpenSSL libssl library, but it is not linked into any process with open internet sockets - meaning that a default installation is technically affected by this bug, but is not vulnerable. Unsupported 3rd party software/scripts that start non-default services or use the library present on the VA may be vulnerable to the bug. Custom Health Monitors using commands that use openssl, e.g. wget, curl, or openssl s_client are vulnerable to a malicious MITM server. You can also use this tool for offline testing as I don't trust the online checkers. https://github.com/FiloSottile/Heartbleed
... View more