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