File: [local] / www / errata45.html (download) (as text)
Revision 1.43, Mon May 11 11:18:29 2015 UTC (9 years ago) by sthen
Branch: MAIN
Changes since 1.42: +1 -0 lines
Add 'link rel="canonical"' to pages, acting as a hint to search engines
to list the copies on www.openbsd.org rather than mirrors.
From Carlin Bingham, ok millert@ nick@
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>OpenBSD 4.5 errata</title>
<meta name="resource-type" content="document">
<meta name="description" content="the OpenBSD CD errata page">
<meta name="keywords" content="openbsd,cd,errata">
<meta name="distribution" content="global">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<link rel="canonical" href="http://www.openbsd.org/errata45.html">
</head>
<!--
IMPORTANT REMINDER
IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
-->
<body bgcolor="#ffffff" text="#000000" link="#23238E">
<a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
<h2><font color="#e00000">
OpenBSD 4.5 errata
</font></h2>
<hr>
<a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
<br>
For errata on a certain release, click below:<br>
<a href="errata21.html">2.1</a>,
<a href="errata22.html">2.2</a>,
<a href="errata23.html">2.3</a>,
<a href="errata24.html">2.4</a>,
<a href="errata25.html">2.5</a>,
<a href="errata26.html">2.6</a>,
<a href="errata27.html">2.7</a>,
<a href="errata28.html">2.8</a>,
<a href="errata29.html">2.9</a>,
<a href="errata30.html">3.0</a>,
<a href="errata31.html">3.1</a>,
<a href="errata32.html">3.2</a>,
<a href="errata33.html">3.3</a>,
<a href="errata34.html">3.4</a>,
<a href="errata35.html">3.5</a>,
<a href="errata36.html">3.6</a>,
<br>
<a href="errata37.html">3.7</a>,
<a href="errata38.html">3.8</a>,
<a href="errata39.html">3.9</a>,
<a href="errata40.html">4.0</a>,
<a href="errata41.html">4.1</a>,
<a href="errata42.html">4.2</a>,
<a href="errata43.html">4.3</a>,
<a href="errata44.html">4.4</a>,
<a href="errata46.html">4.6</a>,
<a href="errata47.html">4.7</a>,
<a href="errata48.html">4.8</a>,
<a href="errata49.html">4.9</a>,
<a href="errata50.html">5.0</a>,
<a href="errata51.html">5.1</a>,
<a href="errata52.html">5.2</a>,
<a href="errata53.html">5.3</a>,
<br>
<a href="errata54.html">5.4</a>,
<a href="errata55.html">5.5</a>,
<a href="errata56.html">5.6</a>,
<a href="errata57.html">5.7</a>.
<br>
<hr>
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.5.tar.gz">
You can also fetch a tar.gz file containing all the following patches</a>.
This file is updated once a day.
<p>
The patches below are available in CVS via the
<code>OPENBSD_4_5</code> <a href="stable.html">patch branch</a>.
<p>
For more detailed information on how to install patches to OpenBSD, please
consult the <a href="./faq/faq10.html#Patches">OpenBSD FAQ</a>.
<p>
<hr>
<ul>
<li id="016_openssl">
<font color="#009000"><strong>016: SECURITY FIX: April 14, 2010</strong></font>
<i>All architectures</i><br>
In TLS connections, certain incorrectly formatted records can cause
an OpenSSL client or server to crash due to a read attempt at NULL.
<br>
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/016_openssl.patch">
A source code patch exists which remedies this problem.</a>
<p>
<li id="015_mpi">
<font color="#009000"><strong>015: RELIABILITY FIX: April 4, 2010</strong></font>
<i>All architectures</i><br>
When updating sensors showing the state of RAID volumes
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mpi&sektion=4">mpi(4)</a>
allocates temporary memory and then returns it to the kernel as
device memory.
This causes kernel memory usage to be misrepresented, eventually
leading to a denial of service when a resource limit is apparently
reached.
<br>
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/015_mpi.patch">
A source code patch exists which remedies this problem.</a>
<p>
<li id="014_kerberos">
<font color="#009000"><strong>014: RELIABILITY FIX: March 31, 2010</strong></font>
<i>All architectures</i><br>
When decrypting packets, the internal decryption functions were not
paranoid enough in checking for underruns, which could potentially
lead to crashes.
<br>
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/014_kerberos.patch">
A source code patch exists which remedies this problem.</a>
<p>
<li id="013_ftpd">
<font color="#009000"><strong>013: RELIABILITY FIX: March 12, 2010</strong></font>
<i>All architectures</i><br>
Due to a null pointer dereference, it would be possible to crash ftpd when
handling glob(3)'ing requests. This is non-exploitable.
<br>
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/013_ftpd.patch">
A source code patch exists which remedies this problem.</a>
<p>
<li id="012_openssl">
<font color="#009000"><strong>012: SECURITY FIX: March 12, 2010</strong></font>
<i>All architectures</i><br>
OpenSSL is susceptible to a buffer overflow due to a failure
to check for NULL returns from bn_wexpand function calls.
<br>
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/012_openssl.patch">
A source code patch exists which remedies this problem.</a>
<p>
<li id="011_ptrace">
<font color="#009000"><strong>011: RELIABILITY FIX: January 29, 2010</strong></font>
<i>All architectures</i><br>
By using ptrace(2) on an ancestor process, a loop in the process tree
could be created, violating assumptions in other parts of the kernel
and resulting in infinite loops.
<br>
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/011_ptrace.patch">
A source code patch exists which remedies this problem.</a>
<p>
<li id="010_openssl">
<font color="#009000"><strong>010: SECURITY FIX: November 26, 2009</strong></font>
<i>All architectures</i><br>
The SSL/TLS protocol is subject to man-in-the-middle attacks related to
renegotiation (see CVE-2009-3555, draft-ietf-tls-renegotiation-00).
OpenSSL permitted this protocol feature by default and had no way to
disable it.
<br>
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/010_openssl.patch">
A source code patch exists which remedies this problem.</a>
<p>
<li id="009_getsockopt">
<font color="#009000"><strong>009: RELIABILITY FIX: October 28, 2009</strong></font>
<i>All architectures</i><br>
getsockopt(2) with any of IP_AUTH_LEVEL, IP_ESP_TRANS_LEVEL, IP_ESP_NETWORK_LEVEL,
IP_IPCOMP_LEVEL will crash the system.
<br>
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/009_getsockopt.patch">
A source code patch exists which remedies this problem.</a>
<p>
<li id="008_xmm">
<font color="#009000"><strong>008: RELIABILITY FIX: October 05, 2009</strong></font>
<i>i386 only</i><br>
XMM exceptions are not correctly handled resulting in a kernel panic.
<br>
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.5/i386/008_xmm.patch">
A source code patch exists which remedies this problem.</a>
<p>
<li id="007_bind">
<font color="#009000"><strong>007: RELIABILITY FIX: July 29, 2009</strong></font>
<i>All architectures</i><br>
A vulnerability has been found in BIND's named server
(<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0696">CVE-2009-0696</a>).
An attacker could crash a server with a specially crafted dynamic update message to a
zone for which the server is master.
<br>
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/007_bind.patch">
A source code patch exists which remedies this problem.</a>
<p>
<li id="006_perl">
<font color="#009000"><strong>006: RELIABILITY FIX: June 24, 2009</strong></font>
<i>All architectures</i><br>
An off-by-one error in the inflate function in Zlib.xs in the
Compress::Raw::Zlib perl module before 2.017 (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1391">CVE-2009-1391</a>),
as used in AMaViS, SpamAssassin, and possibly other products,
allows context-dependent attackers to cause a denial of service
(hang or crash) via a crafted zlib compressed stream that
triggers a heap-based buffer overflow.
<br>
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/006_perl_zlib.patch">
A source code patch exists which remedies this problem.</a>
<p>
<li id="005_audio">
<font color="#009000"><strong>005: RELIABILITY FIX: April 24, 2009</strong></font>
<i>All architectures</i><br>
On very high system load, an audio interrupt may occur while the
audio process is filling audio ring buffers. This triggers bogus
(and useless) correction code in the
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=audio&sektion=4">audio(4)</a>
driver causing the audio application to go out of sync, and in turn causing
continuous stuttering until the application is restarted.
<br>
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/005_audio.patch">
A source code patch exists which remedies this problem.</a>
<p>
<li id="004_aucat">
<font color="#009000"><strong>004: RELIABILITY FIX: April 24, 2009</strong></font>
<i>All architectures</i><br>
In server mode when in full-duplex mode (the default)
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=aucat&sektion=1">aucat(1)</a>
will send each synchronization message twice, causing client applications
to think that buffer underruns are occuring. Depending on the
application, this may cause the sound to stutter.
<br>
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/004_aucat.patch">
A source code patch exists which remedies this problem.</a>
<p>
<li id="003_bus_dma">
<font color="#009000"><strong>003: RELIABILITY FIX: April 24, 2009</strong></font>
<i>i386 only</i><br>
When DMA'able memory is mapped by device drivers, the
mapping flags and protection are partially uninitialized.
Depending on the calling context, this may cause devices to misbehave, like
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=audio&sektion=4">audio(4)</a>
to stutter, but other anomalies might be observed for other
device types.
<br>
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.5/i386/003_bus_dma.patch">
A source code patch exists which remedies this problem.</a>
<p>
<li id="002_pf">
<font color="#009000"><strong>002: RELIABILITY FIX: April 11, 2009</strong></font>
<i>All architectures</i><br>
When pf attempts to perform translation on a specially crafted IP datagram,
a null pointer dereference will occur, resulting in a kernel panic.
In certain configurations this may be triggered by a remote attacker.
<br>
Restricting translation rules to protocols that are specific to the IP version
in use, is an effective workaround until the patch can be installed. As an
example, for IPv4 nat/binat/rdr rules you can use:
<pre>
nat/rdr ... inet proto { tcp udp icmp } ...
</pre>
Or for IPv6 nat/binat/rdr rules you can use:
<pre>
nat/rdr ... inet6 proto { tcp udp icmp6 } ...
</pre>
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/002_pf.patch">
A source code patch exists which remedies this problem.</a>
<p>
<li id="001_openssl">
<font color="#009000"><strong>001: RELIABILITY FIX: April 8, 2009</strong></font>
<i>All architectures</i><br>
The OpenSSL ASN.1 handling code could be forced to perform invalid memory
accesses through the use of certain invalid strings
(<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0590">CVE-2009-0590</a>)
or under certain error conditions triggerable by invalid ASN.1 structures
(<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0789">CVE-2009-0789</a>).
These vulnerabilities could be exploited to achieve a
denial-of-service. A more detailed description of these problems is available
in the
<a href="http://www.openssl.org/news/secadv_20090325.txt">OpenSSL security advisory</a>, but note that the other issue described there "Incorrect Error
Checking During CMS verification" relates to code not enabled in OpenBSD.
<br>
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.5/common/001_openssl.patch">
A source code patch exists which remedies this problem.</a>
<p>
</ul>
<hr>
</body>
</html>
![[BACK]](/icons/back.gif){kind=icon}
Return to errata45.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www