Annotation of www/errata44.html, Revision 1.38
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2: <html>
3: <head>
4: <title>OpenBSD 4.4 errata</title>
5: <meta name="resource-type" content="document">
6: <meta name="description" content="the OpenBSD CD errata page">
7: <meta name="keywords" content="openbsd,cd,errata">
8: <meta name="distribution" content="global">
1.10 sthen 9: <meta name="copyright" content="This document copyright 1997-2009 by OpenBSD.">
1.1 deraadt 10: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
11: </head>
12:
13: <body bgcolor="#ffffff" text="#000000" link="#23238E">
14:
15: <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
16: <h2><font color="#0000e0">
17: This is the OpenBSD 4.4 release errata & patch list:
18:
19: </font></h2>
20:
21: <hr>
22: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
23: <br>
24: For errata on a certain release, click below:<br>
25: <a href="errata21.html">2.1</a>,
26: <a href="errata22.html">2.2</a>,
27: <a href="errata23.html">2.3</a>,
28: <a href="errata24.html">2.4</a>,
29: <a href="errata25.html">2.5</a>,
30: <a href="errata26.html">2.6</a>,
31: <a href="errata27.html">2.7</a>,
32: <a href="errata28.html">2.8</a>,
33: <a href="errata29.html">2.9</a>,
34: <a href="errata30.html">3.0</a>,
35: <a href="errata31.html">3.1</a>,
36: <a href="errata32.html">3.2</a>,
37: <a href="errata33.html">3.3</a>,
38: <a href="errata34.html">3.4</a>,
39: <a href="errata35.html">3.5</a>,
40: <a href="errata36.html">3.6</a>,
41: <br>
42: <a href="errata37.html">3.7</a>,
43: <a href="errata38.html">3.8</a>,
44: <a href="errata39.html">3.9</a>,
45: <a href="errata40.html">4.0</a>,
46: <a href="errata41.html">4.1</a>,
47: <a href="errata42.html">4.2</a>,
1.17 deraadt 48: <a href="errata43.html">4.3</a>,
1.22 deraadt 49: <a href="errata45.html">4.5</a>,
1.26 deraadt 50: <a href="errata46.html">4.6</a>,
1.28 deraadt 51: <a href="errata47.html">4.7</a>,
1.30 miod 52: <a href="errata48.html">4.8</a>,
1.31 nick 53: <a href="errata49.html">4.9</a>,
1.32 sthen 54: <a href="errata50.html">5.0</a>,
1.33 deraadt 55: <a href="errata51.html">5.1</a>,
1.34 deraadt 56: <a href="errata52.html">5.2</a>,
1.35 deraadt 57: <a href="errata53.html">5.3</a>,
1.38 ! deraadt 58: <br>
1.36 deraadt 59: <a href="errata54.html">5.4</a>,
60: <a href="errata55.html">5.5</a>.
1.1 deraadt 61: <br>
62: <hr>
63:
1.27 sthen 64: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4.tar.gz">
1.1 deraadt 65: You can also fetch a tar.gz file containing all the following patches</a>.
66: This file is updated once a day.
67:
68: <p> The patches below are available in CVS via the
1.2 deraadt 69: <code>OPENBSD_4_4</code> <a href="stable.html">patch branch</a>.
1.1 deraadt 70:
71: <p>
72: For more detailed information on how to install patches to OpenBSD, please
73: consult the <a href="./faq/faq10.html#Patches">OpenBSD FAQ</a>.
74: <hr>
75:
76: <!-- Temporarily put anchors for all archs here. Remove later. -->
77: <a name="all"></a>
78: <a name="alpha"></a>
79: <a name="amd64"></a>
80: <a name="armish"></a>
81: <a name="cats"></a>
82: <a name="hp300"></a>
83: <a name="hppa"></a>
84: <a name="i386"></a>
85: <a name="luna88k"></a>
86: <a name="mac68k"></a>
87: <a name="macppc"></a>
88: <a name="mvme68k"></a>
89: <a name="mvme88k"></a>
90: <a name="sgi"></a>
91: <a name="sparc"></a>
92: <a name="sparc64"></a>
93: <a name="vax"></a>
94: <a name="zaurus"></a>
95:
96: <ul>
1.25 deraadt 97: <li><a name="016_getsockopt"></a>
98: <font color="#009000"><strong>016: RELIABILITY FIX: October 28, 2009</strong></font> <i>All architectures</i><br>
99: getsockopt(2) with any of IP_AUTH_LEVEL, IP_ESP_TRANS_LEVEL, IP_ESP_NETWORK_LEVEL,
100: IP_IPCOMP_LEVEL will crash the system.
101: <br>
1.27 sthen 102: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/common/016_getsockopt.patch">
1.25 deraadt 103: A source code patch exists which remedies this problem</a>.<br>
104: <p>
105:
1.24 jsing 106: <li><a name="015_xmm"></a>
107: <font color="#009000"><strong>015: RELIABILITY FIX: October 05, 2009</strong></font> <i>i386 only</i><br>
108: XMM exceptions are not correctly handled resulting in a kernel panic.
109: <br>
1.27 sthen 110: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/i386/015_xmm.patch">
1.24 jsing 111: A source code patch exists which remedies this problem</a>.<br>
112: <p>
113:
1.21 jasper 114: <li><a name="014_bind"></a>
115: <font color="#009000"><strong>014: RELIABILITY FIX: July 29, 2009</strong></font> <i>All architectures</i><br>
116: A vulnerability has been found in BIND's named server
117: (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0696">CVE-2009-0696</a>).
118: An attacker could crash a server with a specially crafted dynamic update message to a
119: zone for which the server is master.
120: <br>
1.27 sthen 121: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/common/014_bind.patch">
1.21 jasper 122: A source code patch exists which remedies this problem</a>.<br>
123: <p>
1.1 deraadt 124:
1.18 sthen 125: <li><a name="013_pf"></a>
126: <font color="#009000"><strong>013: RELIABILITY FIX: April 11, 2009</strong></font> <i>All architectures</i><br>
127: When pf attempts to perform translation on a specially crafted IP datagram,
128: a null pointer dereference will occur, resulting in a kernel panic.
129: In certain configurations this may be triggered by a remote attacker.
1.19 sthen 130: <br>
1.18 sthen 131: Restricting translation rules to protocols that are specific to the IP version
132: in use, is an effective workaround until the patch can be installed. As an
133: example, for IPv4 nat/binat/rdr rules you can use:
134: <pre>
135: nat/rdr ... inet proto { tcp udp icmp } ...
136: </pre>
137: Or for IPv6 nat/binat/rdr rules you can use:
138: <pre>
139: nat/rdr ... inet6 proto { tcp udp icmp6 } ...
140: </pre>
1.27 sthen 141: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/common/013_pf.patch">
1.18 sthen 142: A source code patch exists which remedies this problem</a>.<br>
143: <p>
144:
1.15 djm 145: <li><a name="012_openssl"></a>
146: <font color="#009000"><strong>012: RELIABILITY FIX: April 8, 2009</strong></font> <i>All architectures</i><br>
147: The OpenSSL ASN.1 handling code could be forced to perform invalid memory
1.20 tobias 148: accesses through the use of certain invalid strings
1.15 djm 149: (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0590">CVE-2009-0590</a>)
150: or under certain error conditions triggerable by invalid ASN.1 structures
151: (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0789">CVE-2009-0789</a>).
152: These vulnerabilities could be exploited to achieve a
153: denial-of-service. A more detailed description of these problems is available
154: in the
155: <a href="http://www.openssl.org/news/secadv_20090325.txt">OpenSSL security advisory</a>, but note that the other issue described there "Incorrect Error
156: Checking During CMS verification" relates to code not enabled in OpenBSD.
157: <br>
1.27 sthen 158: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/common/012_openssl.patch">
1.15 djm 159: A source code patch exists which remedies this problem</a>.<br>
160: <p>
161:
1.14 millert 162: <li><a name="011_sudo"></a>
163: <font color="#009000"><strong>011: SECURITY FIX: February 22, 2009</strong></font> <i>All architectures</i><br>
164: sudo(8) may allow a user listed in the sudoers file to run a command
165: as a different user than their access rule specifies when a Unix
166: group is used in the RunAs portion of the rule. The bug only manifests
167: when the user being granted privileges is also a member of the group
168: in the RunAs portion of the rule.
169: <br>
1.27 sthen 170: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/common/011_sudo.patch">
1.14 millert 171: A source code patch exists which remedies this problem</a>.<br>
172: <p>
173:
1.13 claudio 174: <li><a name="010_bgpd"></a>
175: <font color="#009000"><strong>010: RELIABILITY FIX: February 18, 2009</strong></font> <i>All architectures</i><br>
176: bgpd(8) did not correctly prepend its own AS to very long AS paths, causing
177: the process to terminate because of the resulting corrupt path.
178: <br>
1.27 sthen 179: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/common/010_bgpd.patch">
1.13 claudio 180: A source code patch exists which remedies this problem</a>.<br>
181: <p>
182:
1.11 claudio 183: <li><a name="009_bgpd"></a>
184: <font color="#009000"><strong>009: RELIABILITY FIX: January 30, 2009</strong></font> <i>All architectures</i><br>
185: Upon reception of an invalid update with 4-byte AS attributes, bgpd -
186: adhering to the RFCs - closed the session to the neighbor.
187: This error in the specification allowed 3rd parties to close remote BGP
188: sessions.
189: In the worst case Internet connectivity could be lost.
190: <br>
1.27 sthen 191: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/common/009_bgpd.patch">
1.11 claudio 192: A source code patch exists which remedies this problem</a>.<br>
193: <p>
194:
1.9 djm 195: <li><a name="008_bind"></a>
196: <font color="#009000"><strong>008: SECURITY FIX: January 14, 2009</strong></font> <i>All architectures</i><br>
197: named(8) did not correctly check the return value of a DSA verification
198: function, potentially allowing bypass of verification of DNSSEC DSA
199: signatures.
200: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0025">CVE-2009-0025</a>.
201: <br>
1.27 sthen 202: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/common/008_bind.patch">
1.9 djm 203: A source code patch exists which remedies this problem</a>.<br>
204: <p>
205:
1.8 djm 206: <li><a name="007_openssl"></a>
207: <font color="#009000"><strong>007: SECURITY FIX: January 9, 2009</strong></font> <i>All architectures</i><br>
208: The OpenSSL libraries did not correctly check the return value from
1.12 miod 209: certain verification functions, allowing validation to be bypassed and
1.8 djm 210: permitting a remote attacker to conduct a "man in the middle attack"
211: against SSL/TLS connections if the server is configured with a DSA or ECDSA
212: certificate.
213: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5077">CVE-2008-5077</a>.
214: <br>
1.27 sthen 215: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/common/007_openssl.patch">
1.8 djm 216: A source code patch exists which remedies this problem</a>.<br>
217: <p>
218:
1.7 brad 219: <li><a name="006_dhcpd"></a>
220: <font color="#009000"><strong>006: RELIABILITY FIX: November 19, 2008</strong></font> <i>All architectures</i><br>
221: Due to changes in the options handling this caused problems with some
222: DHCP clients such as Solaris/OpenSolaris and some embedded routers not
223: accepting DHCP offers.
224: <br>
1.27 sthen 225: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/common/006_dhcpd.patch">
1.7 brad 226: A source code patch exists which remedies this problem</a>.<br>
227: <p>
228:
1.6 brad 229: <li><a name="005_pglistalloc"></a>
230: <font color="#009000"><strong>005: RELIABILITY FIX: November 7, 2008</strong></font> <i>All architectures</i><br>
231: A software bug could cause memory allocation to cause a kernel panic
232: accessing an array out of its bounds, when physical memory is exhausted.
233: <br>
1.27 sthen 234: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/common/005_pglistalloc.patch">
1.6 brad 235: A source code patch exists which remedies this problem</a>.<br>
236: <p>
237:
1.4 brad 238: <li><a name="004_httpd"></a>
239: <font color="#009000"><strong>004: RELIABILITY FIX: November 6, 2008</strong></font> <i>All architectures</i><br>
240: Fix
241: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=httpd&sektion=8">httpd(8)</a>'s
242: mod_proxy module which is broken on 64-bit architectures. Due to the bug this
243: will result in child processes crashing when utilizing proxy rules during an
244: HTTP session.
245: <br>
1.27 sthen 246: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/common/004_httpd.patch">
1.4 brad 247: A source code patch exists which remedies this problem</a>.<br>
248: <p>
249:
250: <li><a name="003_tcpinput"></a>
251: <font color="#009000"><strong>003: RELIABILITY FIX: November 6, 2008</strong></font> <i>All architectures</i><br>
1.5 brad 252: Fix the IPv4 TCP/IP stack's TIME_WAIT socket recycling. Due to the bug this
1.4 brad 253: can result in TCP connections between two IPs being reset instead of accepted
254: if being received on a socket in the TIME_WAIT state.
255: <br>
1.27 sthen 256: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/common/003_tcpinput.patch">
1.4 brad 257: A source code patch exists which remedies this problem</a>.<br>
258: <p>
259:
1.3 brad 260: <li><a name="002_vr"></a>
261: <font color="#009000"><strong>002: RELIABILITY FIX: November 2, 2008</strong></font> <i>All architectures</i><br>
262: Due to a bug in the vr(4) driver it is possible for a system using the vr(4)
263: driver to panic under heavy load if the RX path runs out of mbufs.
264: <br>
1.27 sthen 265: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/common/002_vr.patch">
1.3 brad 266: A source code patch exists which remedies this problem</a>.<br>
267: <p>
268:
269: <li><a name="001_ndp"></a>
270: <font color="#009000"><strong>001: SECURITY FIX: November 2, 2008</strong></font> <i>All architectures</i><br>
271: The Neighbor Discovery Protocol (ndp) did not correctly verify neighbor
272: solicitation requests maybe allowing a nearby attacker to intercept traffic.
273: The attacker must have IPv6 connectivity to the same router as their target for
274: this vulnerability to be exploited.
275: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2476">CVE-2008-2476</a>.
276: <br>
1.27 sthen 277: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.4/common/001_ndp.patch">
1.3 brad 278: A source code patch exists which remedies this problem</a>.<br>
279: <p>
1.1 deraadt 280:
281: </ul>
282:
283: </body>
284: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to errata44.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www