RHSA-2010:0163: Moderate: openssl security update

Published Mar 25, 2010
·
Updated

OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL v2/v3)and Transport Layer Security (TLS v1) protocols, as well as afull-strength, general purpose cryptography library.A flaw was found in the way the TLS/SSL (Transport Layer Security/SecureSockets Layer) protocols handled session renegotiation. A man-in-the-middleattacker could use this flaw to prefix arbitrary plain text to a client'ssession (for example, an HTTPS connection to a website). This could forcethe server to process an attacker's request as if authenticated using thevictim's credentials. This update addresses this flaw by implementing theTLS Renegotiation Indication Extension, as defined in RFC 5746.(CVE-2009-3555)Refer to the following Knowledgebase article for additional details aboutthe CVE-2009-3555 flaw: http://kbase.redhat.com/faq/docs/DOC-20491 Dan Kaminsky found that browsers could accept certificates with MD2 hashsignatures, even though MD2 is no longer considered a cryptographicallystrong algorithm. This could make it easier for an attacker to create amalicious certificate that would be treated as trusted by a browser.OpenSSL now disables the use of the MD2 algorithm inside signatures bydefault. (CVE-2009-2409)An input validation flaw was found in the handling of the BMPString andUniversalString ASN1 string types in OpenSSL's ASN1STRINGprintex()function. An attacker could use this flaw to create a specially-craftedX.509 certificate that could cause applications using the affected functionto crash when printing certificate contents. (CVE-2009-0590)Note: The affected function is rarely used. No application shipped with RedHat Enterprise Linux calls this function, for example.All OpenSSL users should upgrade to these updated packages, which containbackported patches to resolve these issues. For the update to take effect,all services linked to the OpenSSL library must be restarted, or the systemrebooted.

Affected Software

6 affected componentsFixes available
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

Remediation

Event History

Mar 25, 2010
Advisory Published
via Red Hat·12:00 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of RHSA-2010:0163?

The severity of RHSA-2010:0163 is critical due to a flaw in OpenSSL affecting TLS/SSL protocols.

2

How do I fix RHSA-2010:0163?

To fix RHSA-2010:0163, update OpenSSL packages to version 0.9.7a-43.17.el4_8.5.

3

Which software is affected by RHSA-2010:0163?

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.

4

What vulnerabilities does RHSA-2010:0163 address?

RHSA-2010:0163 addresses vulnerabilities in OpenSSL that could lead to security issues in TLS/SSL communications.

5

Is there a need to reboot my system after applying RHSA-2010:0163?

Generally, a reboot may be required to apply the updates for RHSA-2010:0163, depending on the services that utilize OpenSSL.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203