First published: Thu Mar 25 2010(Updated: )
OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL v2/v3)<br>and Transport Layer Security (TLS v1) protocols, as well as a<br>full-strength, general purpose cryptography library.<br>A flaw was found in the way the TLS/SSL (Transport Layer Security/Secure<br>Sockets Layer) protocols handled session renegotiation. A man-in-the-middle<br>attacker could use this flaw to prefix arbitrary plain text to a client's<br>session (for example, an HTTPS connection to a website). This could force<br>the server to process an attacker's request as if authenticated using the<br>victim's credentials. This update addresses this flaw by implementing the<br>TLS Renegotiation Indication Extension, as defined in RFC 5746.<br>(CVE-2009-3555)<br>Refer to the following Knowledgebase article for additional details about<br>the CVE-2009-3555 flaw: <a href="http://kbase.redhat.com/faq/docs/DOC-20491" target="_blank">http://kbase.redhat.com/faq/docs/DOC-20491</a> Dan Kaminsky found that browsers could accept certificates with MD2 hash<br>signatures, even though MD2 is no longer considered a cryptographically<br>strong algorithm. This could make it easier for an attacker to create a<br>malicious certificate that would be treated as trusted by a browser.<br>OpenSSL now disables the use of the MD2 algorithm inside signatures by<br>default. (CVE-2009-2409)<br>An input validation flaw was found in the handling of the BMPString and<br>UniversalString ASN1 string types in OpenSSL's ASN1_STRING_print_ex()<br>function. An attacker could use this flaw to create a specially-crafted<br>X.509 certificate that could cause applications using the affected function<br>to crash when printing certificate contents. (CVE-2009-0590)<br>Note: The affected function is rarely used. No application shipped with Red<br>Hat Enterprise Linux calls this function, for example.<br>All OpenSSL users should upgrade to these updated packages, which contain<br>backported patches to resolve these issues. For the update to take effect,<br>all services linked to the OpenSSL library must be restarted, or the system<br>rebooted.
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/openssl | <0.9.7a-43.17.el4_8.5 | 0.9.7a-43.17.el4_8.5 |
redhat/openssl | <0.9.7a-43.17.el4_8.5 | 0.9.7a-43.17.el4_8.5 |
redhat/openssl-devel | <0.9.7a-43.17.el4_8.5 | 0.9.7a-43.17.el4_8.5 |
redhat/openssl-devel | <0.9.7a-43.17.el4_8.5 | 0.9.7a-43.17.el4_8.5 |
redhat/openssl-perl | <0.9.7a-43.17.el4_8.5 | 0.9.7a-43.17.el4_8.5 |
redhat/openssl-perl | <0.9.7a-43.17.el4_8.5 | 0.9.7a-43.17.el4_8.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of RHSA-2010:0163 is critical due to a flaw in OpenSSL affecting TLS/SSL protocols.
To fix RHSA-2010:0163, update OpenSSL packages to version 0.9.7a-43.17.el4_8.5.
The affected software for RHSA-2010:0163 includes OpenSSL, OpenSSL-devel, and OpenSSL-perl versions prior to 0.9.7a-43.17.el4_8.5.
RHSA-2010:0163 addresses vulnerabilities in OpenSSL that could lead to security issues in TLS/SSL communications.
Generally, a reboot may be required to apply the updates for RHSA-2010:0163, depending on the services that utilize OpenSSL.