Annotation of www/errata47.html, Revision 1.45
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2: <html>
3: <head>
1.44 tj 4: <title>OpenBSD 4.7 Errata</title>
1.1 deraadt 5: <meta name="description" content="the OpenBSD CD errata page">
6: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
1.43 deraadt 7: <meta name="viewport" content="width=device-width, initial-scale=1">
8: <link rel="stylesheet" type="text/css" href="openbsd.css">
1.37 sthen 9: <link rel="canonical" href="http://www.openbsd.org/errata47.html">
1.1 deraadt 10: </head>
11:
1.33 deraadt 12: <!--
13: IMPORTANT REMINDER
14: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
15: -->
16:
1.1 deraadt 17: <body bgcolor="#ffffff" text="#000000" link="#23238E">
18:
1.43 deraadt 19: <h2>
20: <a href="index.html">
21: <font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>
1.44 tj 22: <font color="#e00000">4.7 Errata</font>
23: </h2>
1.43 deraadt 24: <hr>
1.1 deraadt 25:
26: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
27: <br>
28: For errata on a certain release, click below:<br>
29: <a href="errata21.html">2.1</a>,
30: <a href="errata22.html">2.2</a>,
31: <a href="errata23.html">2.3</a>,
32: <a href="errata24.html">2.4</a>,
33: <a href="errata25.html">2.5</a>,
34: <a href="errata26.html">2.6</a>,
35: <a href="errata27.html">2.7</a>,
36: <a href="errata28.html">2.8</a>,
37: <a href="errata29.html">2.9</a>,
38: <a href="errata30.html">3.0</a>,
39: <a href="errata31.html">3.1</a>,
40: <a href="errata32.html">3.2</a>,
41: <a href="errata33.html">3.3</a>,
42: <a href="errata34.html">3.4</a>,
43: <a href="errata35.html">3.5</a>,
44: <a href="errata36.html">3.6</a>,
45: <br>
46: <a href="errata37.html">3.7</a>,
47: <a href="errata38.html">3.8</a>,
48: <a href="errata39.html">3.9</a>,
49: <a href="errata40.html">4.0</a>,
50: <a href="errata41.html">4.1</a>,
51: <a href="errata42.html">4.2</a>,
52: <a href="errata43.html">4.3</a>,
53: <a href="errata44.html">4.4</a>,
54: <a href="errata45.html">4.5</a>,
1.15 deraadt 55: <a href="errata46.html">4.6</a>,
1.21 miod 56: <a href="errata48.html">4.8</a>,
1.22 nick 57: <a href="errata49.html">4.9</a>,
1.23 sthen 58: <a href="errata50.html">5.0</a>,
1.24 deraadt 59: <a href="errata51.html">5.1</a>,
1.25 deraadt 60: <a href="errata52.html">5.2</a>,
1.26 deraadt 61: <a href="errata53.html">5.3</a>,
1.29 deraadt 62: <br>
1.27 deraadt 63: <a href="errata54.html">5.4</a>,
1.32 jsg 64: <a href="errata55.html">5.5</a>,
1.36 deraadt 65: <a href="errata56.html">5.6</a>,
1.39 deraadt 66: <a href="errata57.html">5.7</a>,
1.40 deraadt 67: <a href="errata58.html">5.8</a>,
1.45 ! deraadt 68: <a href="errata59.html">5.9</a>,
! 69: <a href="errata60.html">6.0</a>.
1.1 deraadt 70: <br>
71: <hr>
72:
1.13 sthen 73: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7.tar.gz">
1.1 deraadt 74: You can also fetch a tar.gz file containing all the following patches</a>.
75: This file is updated once a day.
1.30 deraadt 76: <p>
1.1 deraadt 77:
1.30 deraadt 78: The patches below are available in CVS via the
1.2 deraadt 79: <code>OPENBSD_4_7</code> <a href="stable.html">patch branch</a>.
1.30 deraadt 80: <p>
1.1 deraadt 81:
82: For more detailed information on how to install patches to OpenBSD, please
83: consult the <a href="./faq/faq10.html#Patches">OpenBSD FAQ</a>.
1.30 deraadt 84: <p>
85:
1.1 deraadt 86: <hr>
87:
88: <ul>
1.34 bentley 89: <li id="013_pf">
1.31 deraadt 90: <font color="#009000"><strong>013: SECURITY FIX: February 16, 2011</strong></font>
91: <i>Little-endian architectures</i><br>
1.20 sthen 92: PF rules specifying address ranges (e.g. "10.1.1.1 - 10.1.1.5") were
93: not correctly handled on little-endian systems (alpha, amd64, arm, i386,
94: mips64el, vax). Other address types (bare addresses "10.1.1.1" and
95: prefixes "10.1.1.1/30") are not affected.
96: <br>
97: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/013_pf.patch">
1.30 deraadt 98: A source code patch exists which remedies this problem.</a>
1.20 sthen 99: <p>
100:
1.34 bentley 101: <li id="012_openssl">
1.31 deraadt 102: <font color="#009000"><strong>012: SECURITY FIX: February 11, 2011</strong></font>
103: <i>All architectures</i><br>
1.20 sthen 104: An incorrectly formatted ClientHello handshake message could cause
105: OpenSSL to parse past the end of the message. An attacker could use this flaw
106: to trigger an invalid memory access, causing a crash of an application linked
107: to OpenSSL. As well, certain applications may expose the contents of parsed
108: OCSP extensions, specifically the OCSP nonce extension.
109: <p>
110: Applications are only affected if they act as a server and call
111: SSL_CTX_set_tlsext_status_cb on the server's SSL_CTX. It is believed
112: that nothing in the base OS uses this. Apache httpd started using this
1.27 deraadt 113: in v2.3.3; this is newer than the version in ports.
1.20 sthen 114: <br>
115: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/012_openssl.patch">
1.30 deraadt 116: A source code patch exists which remedies this problem.</a>
1.20 sthen 117: <p>
118:
1.34 bentley 119: <li id="011_rtsock">
1.31 deraadt 120: <font color="#009000"><strong>011: RELIABILITY FIX: January 13, 2011</strong></font>
121: <i>All architectures</i><br>
1.19 jsg 122: sp_protocol in RTM_DELETE messages could contain garbage values
123: leading to routing socket users that restrict the AF (such as ospfd)
124: not seeing any of the RTM_DELETE messages.
125: <br>
126: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/011_rtsock.patch">
1.30 deraadt 127: A source code patch exists which remedies this problem.</a>
1.19 jsg 128: <p>
129:
1.34 bentley 130: <li id="010_cbc">
1.31 deraadt 131: <font color="#009000"><strong>010: RELIABILITY FIX: December 20, 2010</strong></font>
132: <i>All architectures</i><br>
1.18 jasper 133: Bring CBC oracle attack countermeasures to hardware crypto accelerator land.
134: This fixes aes-ni, via xcrypt and various drivers
1.42 sthen 135: (<a href="http://man.openbsd.org/?query=glxsb&arch=i386&sektion=4">glxsb(4)</a>,
136: <a href="http://man.openbsd.org/?query=hifn&sektion=4">hifn(4)</a>,
137: <a href="http://man.openbsd.org/?query=safe&sektion=4">safe(4)</a>
1.18 jasper 138: and
1.42 sthen 139: <a href="http://man.openbsd.org/?query=ubsec&sektion=4">ubsec(4)</a>).
1.18 jasper 140:
141: <br>
142: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/010_cbc.patch">
1.30 deraadt 143: A source code patch exists which remedies this problem.</a>
1.18 jasper 144: <p>
145:
146:
1.34 bentley 147: <li id="009_pf">
1.31 deraadt 148: <font color="#009000"><strong>009: SECURITY FIX: December 17, 2010</strong></font>
149: <i>All architectures</i><br>
1.17 jasper 150: Insufficent initialization of the pf rule structure in the ioctl
151: handler may allow userland to modify kernel memory. By default root
152: privileges are needed to add or modify pf rules.
153: <br>
154: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/009_pf.patch">
1.30 deraadt 155: A source code patch exists which remedies this problem.</a>
1.17 jasper 156: <p>
157:
1.34 bentley 158: <li id="008_openssl">
1.31 deraadt 159: <font color="#009000"><strong>008: RELIABILITY FIX: November 17, 2010</strong></font>
160: <i>All architectures</i><br>
1.16 jasper 161: Fix a flaw in the OpenSSL TLS server extension code parsing which could lead to
162: a buffer overflow. This affects OpenSSL based TLS servers which are multi-threaded
163: and use OpenSSL's internal caching mechanism. Servers that are multi-process
164: and/or disable internal session caching are not affected.
165: <br>
166: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/008_openssl.patch">
1.30 deraadt 167: A source code patch exists which remedies this problem.</a>
1.16 jasper 168: <p>
169:
1.34 bentley 170: <li id="007_scsi">
1.31 deraadt 171: <font color="#009000"><strong>007: RELIABILITY FIX: September 14, 2010</strong></font>
172: <i>All architectures</i><br>
1.14 stephan 173: Avoid calling scsi_done() more than once in gdt(4). Fixes a kernel panic triggered by syncing disks during shut down.<br>
174: Clear the ITSDONE flag before issuing commands to the SCSI adapter. Fixes handling of retried SCSI commands.
175: <br>
176: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/007_scsi.patch">
1.30 deraadt 177: A source code patch exists which remedies this problem.</a>
1.14 stephan 178: <p>
179:
1.34 bentley 180: <li id="006_scsi">
1.31 deraadt 181: <font color="#009000"><strong>006: RELIABILITY FIX: July 8, 2010</strong></font>
182: <i>All architectures</i><br>
1.12 stephan 183: Restore an unusual XS_SENSE semantic. Fixes dump(8)/restore(8) problems seen on certain tape drives.
184: <br>
1.13 sthen 185: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/006_scsi.patch">
1.30 deraadt 186: A source code patch exists which remedies this problem.</a>
1.12 stephan 187: <p>
188:
1.34 bentley 189: <li id="005_pfsync">
1.31 deraadt 190: <font color="#009000"><strong>005: RELIABILITY FIX: May 14, 2010</strong></font>
191: <i>All architectures</i><br>
1.10 stephan 192: Incorrectly initialized state updates can cause pfsync update storms.
193: <br>
1.13 sthen 194: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/005_pfsync.patch">
1.30 deraadt 195: A source code patch exists which remedies this problem.</a>
1.10 stephan 196: <p>
197:
1.34 bentley 198: <li id="004_pfsync">
1.31 deraadt 199: <font color="#009000"><strong>004: SECURITY FIX: April 23, 2010</strong></font>
200: <i>All architectures</i><br>
1.9 pyr 201: The combination of pfsync and IPSEC may crash the kernel.<br>
1.13 sthen 202: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/004_pfsync.patch">
1.30 deraadt 203: A source code patch exists which remedies this problem.</a>
1.9 pyr 204: <p>
205:
1.34 bentley 206: <li id="003_openssl">
1.31 deraadt 207: <font color="#009000"><strong>003: SECURITY FIX: April 14, 2010</strong></font>
208: <i>All architectures</i><br>
1.8 jasper 209: In TLS connections, certain incorrectly formatted records can cause
210: an OpenSSL client or server to crash due to a read attempt at NULL.
211: <br>
1.13 sthen 212: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/003_openssl.patch">
1.30 deraadt 213: A source code patch exists which remedies this problem.</a>
1.8 jasper 214: <p>
1.7 jasper 215:
1.34 bentley 216: <li id="002_mpi">
1.31 deraadt 217: <font color="#009000"><strong>002: RELIABILITY FIX: April 4, 2010</strong></font>
218: <i>All architectures</i><br>
1.4 dlg 219: When updating sensors showing the state of RAID volumes
1.42 sthen 220: <a href="http://man.openbsd.org/?query=mpi&sektion=4">mpi(4)</a>
1.4 dlg 221: allocates temporary memory and then returns it to the kernel as
222: device memory.
223: This causes kernel memory usage to be misrepresented, eventually
224: leading to a denial of service when a resource limit is apparently
225: reached.
226: <br>
1.13 sthen 227: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/002_mpi.patch">
1.30 deraadt 228: A source code patch exists which remedies this problem.</a>
1.4 dlg 229: <p>
230:
1.34 bentley 231: <li id="001_kerberos">
1.31 deraadt 232: <font color="#009000"><strong>001: RELIABILITY FIX: March 31, 2010</strong></font>
233: <i>All architectures</i><br>
1.3 jasper 234: When decrypting packets, the internal decryption functions were not
235: paranoid enough in checking for underruns, which could potentially
236: lead to crashes.
237: <br>
1.13 sthen 238: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/4.7/common/001_kerberos.patch">
1.30 deraadt 239: A source code patch exists which remedies this problem.</a>
1.3 jasper 240: <p>
1.28 deraadt 241:
1.1 deraadt 242: </ul>
243:
1.35 tedu 244: <hr>
245:
1.1 deraadt 246: </body>
247: </html>