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