LANDESK is aware of the vulnerability inside of SSL 3.0 and we are currently finishing the the process of reviewing its impact. We will update this document with further information as we have it. We appreciate your patience.
As updates are available, including any additional information about how this vulnerability affects LANDESK products and progress for any updates or patches, it will be added to this document.
Latest Updates
Resolution of Known issue -
October 17, 2014 (12:10PM MDT)
LANDESK is currently reviewing the impact that disabling SSL 3.0 in the core server and Cloud Service Appliance has on core functionality.
What is this vulnerability?
As Per US-CERT "The SSL 3.0 vulnerability stems from the way blocks of data are encrypted under a specific type of encryption algorithm within the SSL protocol. The POODLE attack takes advantage of the protocol version negotiation feature built into SSL/TLS to force the use of SSL 3.0 and then leverages this new vulnerability to decrypt select content within the SSL session. The decryption is done byte by byte and will generate a large number of connections between the client and server.
While SSL 3.0 is an old encryption standard and has generally been replaced by Transport Layer Security (TLS) (which is not vulnerable in this way), most SSL/TLS implementations remain backwards compatible with SSL 3.0 to interoperate with legacy systems in the interest of a smooth user experience. Even if a client and server both support a version of TLS the SSL/TLS protocol suite allows for protocol version negotiation (being referred to as the “downgrade dance” in other reporting). The POODLE attack leverages the fact that when a secure connection attempt fails, servers will fall back to older protocols such as SSL 3.0. An attacker who can trigger a connection failure can then force the use of SSL 3.0 and attempt the new attack. [1]
Two other conditions must be met to successfully execute the POODLE attack: 1) the attacker must be able to control portions of the client side of the SSL connection (varying the length of the input) and 2) the attacker must have visibility of the resulting ciphertext. The most common way to achieve these conditions would be to act as Man-in-the-Middle (MITM), requiring a whole separate form of attack to establish that level of access.
These conditions make successful exploitation somewhat difficult. Environments that are already at above-average risk for MITM attacks (such as public WiFi) remove some of those challenges."
Read More at http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3566 and SSL 3.0 Protocol Vulnerability and POODLE Attack | US-CERT
How does this affect LANDESK?
Affected Product(s)
LANDESK Management Suite / Security Suite 9.0 and later
LANDESK Cloud Services Appliance 4.2 and later
Non-Affected Product(s)
LANDESK Asset Lifecycle Manager
LANDESK Service Desk, including Service Desk as a Service (SDaas)
Mobility products including Wavelink, Avalanche on Demand, and LANDESK Mobility Management
- LANDESK Support