Annotation of www/errata59.html, Revision 1.25
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2: <html>
3: <head>
1.6 tj 4: <title>OpenBSD 5.9 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.4 deraadt 7: <meta name="viewport" content="width=device-width, initial-scale=1">
8: <link rel="stylesheet" type="text/css" href="openbsd.css">
1.23 tb 9: <link rel="canonical" href="https://www.openbsd.org/errata59.html">
1.1 deraadt 10: </head>
11:
12: <!--
13: IMPORTANT REMINDER
14: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
15: -->
16: <body bgcolor="#ffffff" text="#000000" link="#23238E">
17:
1.4 deraadt 18: <h2>
19: <a href="index.html">
20: <font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>
1.6 tj 21: <font color="#e00000">5.9 Errata</font>
22: </h2>
1.4 deraadt 23: <hr>
1.1 deraadt 24:
25: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
26: <br>
27: For errata on a certain release, click below:<br>
28: <a href="errata21.html">2.1</a>,
29: <a href="errata22.html">2.2</a>,
30: <a href="errata23.html">2.3</a>,
31: <a href="errata24.html">2.4</a>,
32: <a href="errata25.html">2.5</a>,
33: <a href="errata26.html">2.6</a>,
34: <a href="errata27.html">2.7</a>,
35: <a href="errata28.html">2.8</a>,
36: <a href="errata29.html">2.9</a>,
37: <a href="errata30.html">3.0</a>,
38: <a href="errata31.html">3.1</a>,
39: <a href="errata32.html">3.2</a>,
40: <a href="errata33.html">3.3</a>,
41: <a href="errata34.html">3.4</a>,
42: <a href="errata35.html">3.5</a>,
43: <a href="errata36.html">3.6</a>,
44: <br>
45: <a href="errata37.html">3.7</a>,
46: <a href="errata38.html">3.8</a>,
47: <a href="errata39.html">3.9</a>,
48: <a href="errata40.html">4.0</a>,
49: <a href="errata41.html">4.1</a>,
50: <a href="errata42.html">4.2</a>,
51: <a href="errata43.html">4.3</a>,
52: <a href="errata44.html">4.4</a>,
53: <a href="errata45.html">4.5</a>,
54: <a href="errata46.html">4.6</a>,
55: <a href="errata47.html">4.7</a>,
56: <a href="errata48.html">4.8</a>,
57: <a href="errata49.html">4.9</a>,
58: <a href="errata50.html">5.0</a>,
59: <a href="errata51.html">5.1</a>,
60: <a href="errata52.html">5.2</a>,
61: <br>
62: <a href="errata53.html">5.3</a>,
63: <a href="errata54.html">5.4</a>,
64: <a href="errata55.html">5.5</a>,
65: <a href="errata56.html">5.6</a>,
66: <a href="errata57.html">5.7</a>,
1.20 deraadt 67: <a href="errata58.html">5.8</a>,
68: <a href="errata60.html">6.0</a>.
1.1 deraadt 69: <br>
70: <hr>
71:
72: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9.tar.gz">
73: You can also fetch a tar.gz file containing all the following patches</a>.
74: This file is updated once a day.
75: <p>
76:
77: The patches below are available in CVS via the
78: <code>OPENBSD_5_9</code> <a href="stable.html">patch branch</a>.
79: <p>
80:
81: For more detailed information on how to install patches to OpenBSD, please
82: consult the <a href="./faq/faq10.html#Patches">OpenBSD FAQ</a>.
83: <p>
84:
85: <hr>
86:
87: <ul>
88:
1.2 deraadt 89: <li id="001_sshd">
90: <font color="#009000"><strong>001: SECURITY FIX: March 10, 2016</strong></font>
91: <i>All architectures</i><br>
92: <a href="http://www.openssh.com/txt/x11fwd.adv">
93: Lack of credential sanitization allows injection of commands to xauth(1).</a>
94: <br>
95: Prevent this problem immediately by not using the "X11Forwarding" feature
96: (which is disabled by default)
97: <br>
98: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/001_sshd.patch.sig">
99: A source code patch exists which remedies this problem.</a>
100: <p>
1.1 deraadt 101:
1.3 deraadt 102: <li id="002_in6bind">
103: <font color="#009000"><strong>002: SECURITY FIX: March 16, 2016</strong></font>
104: <i>All architectures</i><br>
105: Insufficient checks in IPv6 socket binding and UDP IPv6 option
106: processing allow a local user to send UDP packets with a source
107: (IPv6 address + port) already reserved by another user.
108: <br>
109: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/002_in6bind.patch.sig">
110: A source code patch exists which remedies this problem.</a>
111: <p>
112:
113: <li id="003_pledge">
114: <font color="#009000"><strong>003: RELIABILITY FIX: March 16, 2016</strong></font>
115: <i>All architectures</i><br>
116: Incorrect path processing in pledge_namei() could result in unexpected
117: program termination of pledge(2)'d programs.
118: <br>
119: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/003_pledge.patch.sig">
120: A source code patch exists which remedies this problem.</a>
121: <p>
122:
1.7 sthen 123: <li id="004_mbuf">
124: <font color="#009000"><strong>004: RELIABILITY FIX: April 30, 2016</strong></font>
125: <i>All architectures</i><br>
126: A problem in m_dup_pkt() can result in kernel crashes with carp(4).
127: <br>
128: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/004_mbuf.patch.sig">
129: A source code patch exists which remedies this problem.</a>
130: <p>
131:
1.8 tedu 132: <li id="005_crypto">
133: <font color="#009000"><strong>005: SECURITY FIX: May 3, 2016</strong></font>
134: <i>All architectures</i><br>
135: Fix issues in the libcrypto library.
136: Refer to <a href="https://www.openssl.org/news/secadv/20160503.txt">the advisory</a>.
137: <ul>
138: <li>Memory corruption in the ASN.1 encoder (CVE-2016-2108)
139: <li>Padding oracle in AES-NI CBC MAC check (CVE-2016-2107)
140: <li>EVP_EncodeUpdate overflow (CVE-2016-2105)
141: <li>EVP_EncryptUpdate overflow (CVE-2016-2106)
142: <li>ASN.1 BIO excessive memory allocation (CVE-2016-2109)
143: </ul>
144: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/005_crypto.patch.sig">
145: A source code patch exists which remedies this problem.</a>
146: <p>
147:
1.9 gilles 148: <li id="006_smtpd">
149: <font color="#009000"><strong>006: RELIABILITY FIX: May 16, 2016</strong></font>
150: <i>All architectures</i><br>
151: Fix issues in smtpd.
152: <ul>
153: <li>Fix logic issue in smtp state machine that can lead to invalid state and result in crash.
154: <li>Plug file pointer leak that can lead to resources exhaustion and result in crash.
155: </ul>
156: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/006_smtpd.patch.sig">
157: A source code patch exists which remedies this problem.</a>
158: <p>
159:
1.10 kettenis 160: <li id="007_uvideo">
161: <font color="#009000"><strong>007: SECURITY FIX: May 17, 2016</strong></font>
162: <i>All architectures</i><br>
163: Insufficient checks in the uvideo(4) V4L2 ioctl handling leak kernel
164: memory contents to a local user.
165: <br>
166: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/007_uvideo.patch.sig">
167: A source code patch exists which remedies this problem.</a>
168: <p>
169:
1.11 otto 170: <li id="008_bnx">
171: <font color="#009000"><strong>008: RELIABILITY FIX: May 18, 2016</strong></font>
172: <i>All architectures</i><br>
173: Fix issue in the bnx(4) ethernet driver that could cause data corruption.
1.12 tj 174: <br>
1.11 otto 175: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/008_bnx.patch.sig">
176: A source code patch exists which remedies this problem.</a>
177: <p>
1.13 bcook 178:
179: <li id="009_crypto">
180: <font color="#009000"><strong>009: RELIABILITY FIX: May 29, 2016</strong></font>
181: <i>All architectures</i><br>
182: Fix a bug in the libcrypto library when parsing certain ASN.1 elements.
183: <br>
184: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/009_crypto.patch.sig">
185: A source code patch exists which remedies this problem.</a>
186: <p>
1.14 deraadt 187:
188: <li id="010_libexpat">
189: <font color="#009000"><strong>010: SECURITY FIX: June 2, 2016</strong></font>
190: <i>All architectures</i><br>
191: Fix issues in the libexpat library to prevent multiple integer and
192: buffer overflows.
193: <br>
194: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/010_libexpat.patch.sig">
195: A source code patch exists which remedies this problem.</a>
196: <p>
197:
1.15 awolk 198: <li id="011_crypto">
199: <font color="#009000"><strong>011: SECURITY FIX: June 6, 2016</strong></font>
200: <i>All architectures</i><br>
201: Correct a problem that prevents the DSA signing algorithm from running
202: in constant time even if the flag BN_FLG_CONSTTIME is set.
203: <br>
204: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/011_crypto.patch.sig">
205: A source code patch exists which remedies this problem.</a>
206: <p>
207:
1.16 beck 208: <li id="012_crypto">
209: <font color="#009000"><strong>012: SECURITY FIX: June 27, 2016</strong></font>
210: <i>All architectures</i><br>
211: Correct a problem that could result in incorrect parsing/encoding of times in OCSP messages.
212: <br>
213: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/012_crypto.patch.sig">
214: A source code patch exists which remedies this problem.</a>
215: <p>
216:
1.17 deraadt 217: <li id="013_splice">
218: <font color="#009000"><strong>013: RELIABILITY FIX: July 14, 2016</strong></font>
219: <i>All architectures</i><br>
220: Splicing sockets in a loop could cause a kernel spin.
221: <br>
222: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/013_splice.patch.sig">
223: A source code patch exists which remedies this problem.</a>
224: <p>
225:
226: <li id="014_unp">
227: <font color="#009000"><strong>014: RELIABILITY FIX: July 14, 2016</strong></font>
228: <i>All architectures</i><br>
229: Multiple processes exiting with a fd-passing control message on a
230: shared socket could crash the system.
231: <br>
232: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/014_unp.patch.sig">
233: A source code patch exists which remedies this problem.</a>
234: <p>
235:
236: <li id="015_dirent">
237: <font color="#009000"><strong>015: RELIABILITY FIX: July 14, 2016</strong></font>
238: <i>All architectures</i><br>
239: ufs_readdir failed to limit size of memory allocation, leading to panics.
240: <br>
241: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/015_dirent.patch.sig">
242: A source code patch exists which remedies this problem.</a>
243: <p>
244:
245: <li id="016_mmap">
246: <font color="#009000"><strong>016: SECURITY FIX: July 14, 2016</strong></font>
247: <i>All architectures</i><br>
248: The mmap extension __MAP_NOFAULT could overcommit resources and crash
249: the system.
250: <br>
251: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/016_mmap.patch.sig">
252: A source code patch exists which remedies this problem.</a>
253: <p>
254:
1.18 tj 255: <li id="017_arp">
1.17 deraadt 256: <font color="#009000"><strong>017: RELIABILITY FIX: July 14, 2016</strong></font>
257: <i>All architectures</i><br>
1.18 tj 258: A race occuring in the unlocked ARP input path can lead to a kernel
259: NULL dereference.
260: <br>
261: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/017_arp.patch.sig">
262: A source code patch exists which remedies this problem.</a>
263: <p>
264:
265: <li id="018_timeout">
266: <font color="#009000"><strong>018: RELIABILITY FIX: July 14, 2016</strong></font>
267: <i>All architectures</i><br>
1.17 deraadt 268: Tick counting overflows could cause a kernel crash.
269: <br>
1.18 tj 270: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/018_timeout.patch.sig">
1.17 deraadt 271: A source code patch exists which remedies this problem.</a>
272: <p>
273:
1.18 tj 274: <li id="019_kevent">
275: <font color="#009000"><strong>019: RELIABILITY FIX: July 14, 2016</strong></font>
1.17 deraadt 276: <i>All architectures</i><br>
277: Invalid file descriptor use with kevent(2) could lead to a kernel crash.
278: <br>
1.18 tj 279: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/019_kevent.patch.sig">
1.17 deraadt 280: A source code patch exists which remedies this problem.</a>
281: <p>
282:
1.18 tj 283: <li id="020_amap">
284: <font color="#009000"><strong>020: RELIABILITY FIX: July 14, 2016</strong></font>
1.17 deraadt 285: <i>All architectures</i><br>
286: Unchecked parameters and integer overflows in the amap allocation routines
287: could cause malloc(9) to either not allocate enough memory, leading to memory
288: corruption, or to trigger a "malloc: allocation too large" panic.
289: <br>
1.18 tj 290: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/020_amap.patch.sig">
1.17 deraadt 291: A source code patch exists which remedies this problem.</a>
292: <p>
293:
1.19 benno 294: <li id="021_relayd">
295: <font color="#009000"><strong>021: RELIABILITY FIX: July 25, 2016</strong></font>
296: <i>All architectures</i><br>
297: When signaling an error to an HTTP relay client, the connection can be
298: terminated prematurely, leading to a crash.
299: <br>
300: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/021_relayd.patch.sig">
301: A source code patch exists which remedies this problem.</a>
302: <p>
303:
1.21 tj 304: <li id="022_sysctl">
305: <font color="#009000">
306: <strong>022: RELIABILITY FIX: August 2, 2016</strong></font>
307: <i>All architectures</i>
308: <br>
309: A missing NULL check in sysctl code results in a crash.
310: <br>
311: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/022_sysctl.patch.sig">
312: A source code patch exists which remedies this problem.</a>
313: <p>
314:
315: <li id="023_uvmisavail">
316: <font color="#009000">
317: <strong>023: RELIABILITY FIX: August 2, 2016</strong></font>
318: <i>All architectures</i>
319: <br>
320: Missing overflow checks in uvm may result in panics.
321: <br>
322: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/023_uvmisavail.patch.sig">
323: A source code patch exists which remedies this problem.</a>
324: <p>
325:
1.22 tj 326: <li id="024_perl">
327: <font color="#009000">
328: <strong>024: SECURITY FIX: August 6, 2016</strong></font>
329: <i>All architectures</i>
330: <br>
331: Don't look in the current working directory for perl modules to load.
332: See the <a href="http://marc.info/?l=perl5-porters&m=146945269625067&w=2">
333: perl5-porters announcement</a> for details.
334: <br>
335: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/024_perl.patch.sig">
336: A source code patch exists which remedies this problem.</a>
337: <p>
338:
339: <li id="025_relayd">
340: <font color="#009000">
341: <strong>025: RELIABILITY FIX: August 6, 2016</strong></font>
342: <i>All architectures</i>
343: <br>
344: Improve relayd's parsing of the Host-header by following RFC 7230
345: Section 5.4 more strictly.
346: <br>
347: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/025_relayd.patch.sig">
348: A source code patch exists which remedies this problem.</a>
349: <p>
350:
1.24 tj 351: <li id="026_wsfont">
352: <font color="#009000">
353: <strong>026: RELIABILITY FIX: September 17, 2016</strong></font>
354: <i>All architectures</i>
355: <br>
356: Limit the number of wscons fonts that can be loaded into the kernel.
357: <br>
358: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/026_wsfont.patch.sig">
359: A source code patch exists which remedies this problem.</a>
360: <p>
361:
1.25 ! tj 362: <li id="027_libssl">
! 363: <font color="#009000">
! 364: <strong>027: RELIABILITY FIX: September 22, 2016</strong></font>
! 365: <i>All architectures</i>
! 366: <br>
! 367: Avoid unbounded memory growth in libssl, which can be triggered by a TLS
! 368: client repeatedly renegotiating and sending OCSP Status Request TLS extensions.
! 369: <br>
! 370: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/027_libssl.patch.sig">
! 371: A source code patch exists which remedies this problem.</a>
! 372: <p>
! 373:
! 374: <li id="028_libssl">
! 375: <font color="#009000">
! 376: <strong>028: SECURITY FIX: September 22, 2016</strong></font>
! 377: <i>All architectures</i>
! 378: <br>
! 379: Avoid falling back to a weak digest for (EC)DH when using SNI with libssl.
! 380: <br>
! 381: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/028_libssl.patch.sig">
! 382: A source code patch exists which remedies this problem.</a>
! 383: <p>
! 384:
1.1 deraadt 385: </ul>
386:
387: <hr>
388:
389: </body>
390: </html>