|
 |
| Problem Description |
A number of vulnerabilities were discovered in OpenVPN that were fixed
in the 2.0.1 release:
A DoS attack against the server when run with "verb 0" and without
"tls-auth" when a client connection to the server fails certificate
verification, the OpenSSL error queue is not properly flushed. This
could result in another unrelated client instance on the server seeing
the error and responding to it, resulting in a disconnection of the
unrelated client (CAN-2005-2531).
A DoS attack against the server by an authenticated client that sends
a packet which fails to decrypt on the server, the OpenSSL error queue
was not properly flushed. This could result in another unrelated
client instance on the server seeing the error and responding to it,
resulting in a disconnection of the unrelated client (CAN-2005-2532).
A DoS attack against the server by an authenticated client is possible
in "dev tap" ethernet bridging mode where a malicious client could
theoretically flood the server with packets appearing to come from
hundreds of thousands of different MAC addresses, resulting in the
OpenVPN process exhausting system virtual memory (CAN-2005-2533).
If two or more client machines tried to connect to the server at the
same time via TCP, using the same client certificate, a race condition
could crash the server if --duplicate-cn is not enabled on the server
(CAN-2005-2534).
This update provides OpenVPN 2.0.1 which corrects these issues as well
as a number of other bugs.
| Updated Packages |
Multi Network Firewall 2.0
20daf4b6f9dbc1c53f3b4f4d375262d4 mnf/2.0/RPMS/openvpn-2.0.1-0.1.M20mdk.i586.rpm a92bbc0c8285fecfbe3f439d18a62580 mnf/2.0/SRPMS/openvpn-2.0.1-0.1.M20mdk.src.rpm
| References |
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-2531
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-2532
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-2533
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-2534
| Upgrade |
To upgrade automatically, use MandrivaUpdate.
| Verification |
Please verify the update prior to upgrading to ensure the integrity of the downloaded package. You can do this with the command :
rpm --checksig package.rpm
You can get the GPG public key of the Mandriva Security Team to verify the GPG signature of each RPM.
If you use MandrivaUpdate, the verification of md5 checksum and GPG signature is performed automatically for you.