Annotation of www/errata60.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 6.0 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">
7: <meta name="viewport" content="width=device-width, initial-scale=1">
8: <link rel="stylesheet" type="text/css" href="openbsd.css">
1.24 tj 9: <link rel="canonical" href="https://www.openbsd.org/errata60.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:
18: <h2>
19: <a href="index.html">
20: <font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>
21: <font color="#e00000">6.0 Errata</font>
22: </h2>
23: <hr>
24:
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>,
49: <a href="errata43.html">4.3</a>,
50: <a href="errata44.html">4.4</a>,
51: <a href="errata45.html">4.5</a>,
52: <a href="errata46.html">4.6</a>,
53: <a href="errata47.html">4.7</a>,
54: <a href="errata48.html">4.8</a>,
55: <a href="errata49.html">4.9</a>,
56: <a href="errata50.html">5.0</a>,
57: <a href="errata51.html">5.1</a>,
58: <a href="errata52.html">5.2</a>,
59: <br>
60: <a href="errata53.html">5.3</a>,
61: <a href="errata54.html">5.4</a>,
62: <a href="errata55.html">5.5</a>,
63: <a href="errata56.html">5.6</a>,
64: <a href="errata57.html">5.7</a>,
65: <a href="errata58.html">5.8</a>,
1.24 tj 66: <a href="errata59.html">5.9</a>,
67: <a href="errata61.html">6.1</a>.
1.1 deraadt 68: <hr>
69:
70: <p>
1.24 tj 71: Patches for the OpenBSD base system are distributed as unified diffs.
72: Each patch is cryptographically signed with the
1.35 tb 73: <a href="https://man.openbsd.org/OpenBSD-6.0/signify.1">signify(1)</a> tool and contains
1.24 tj 74: usage instructions.
75: All the following patches are also available in one
76: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0.tar.gz">tar.gz file</a>
77: for convenience.
1.1 deraadt 78:
79: <p>
1.24 tj 80: Patches for supported releases are also incorporated into the
81: <a href="stable.html">-stable branch</a>, which is maintained for one year
82: after release.
1.1 deraadt 83:
84: <hr>
85:
86: <ul>
87:
1.25 tb 88: <li id="p001_uvmisavail">
1.2 tj 89: <font color="#009000">
90: <strong>001: RELIABILITY FIX: August 2, 2016</strong></font>
91: <i>All architectures</i>
92: <br>
93: Missing overflow checks in uvm may result in panics.
94: <br>
1.14 tb 95: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/001_uvmisavail.patch.sig">
1.2 tj 96: A source code patch exists which remedies this problem.</a>
97: <p>
1.1 deraadt 98:
1.25 tb 99: <li id="p002_perl">
1.3 tj 100: <font color="#009000">
101: <strong>002: RELIABILITY FIX: August 6, 2016</strong></font>
102: <i>All architectures</i>
103: <br>
104: Fixes IO::Socket::IP complaining about non-numeric version numbers.
105: <br>
1.14 tb 106: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/002_perl.patch.sig">
1.3 tj 107: A source code patch exists which remedies this problem.</a>
108: <p>
109:
1.25 tb 110: <li id="p003_relayd">
1.3 tj 111: <font color="#009000">
112: <strong>003: RELIABILITY FIX: August 6, 2016</strong></font>
113: <i>All architectures</i>
114: <br>
115: Improve relayd's parsing of the Host-header by following RFC 7230
116: Section 5.4 more strictly.
117: <br>
1.14 tb 118: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/003_relayd.patch.sig">
1.3 tj 119: A source code patch exists which remedies this problem.</a>
120: <p>
121:
1.25 tb 122: <li id="p004_smtpd">
1.5 tj 123: <font color="#009000">
124: <strong>004: RELIABILITY FIX: August 23, 2016</strong></font>
125: <i>All architectures</i>
126: <br>
127: A missing initialization can prevent mail headers from being altered as
128: intended, resulting in mail being sent to incorrect addresses.
129: <br>
1.14 tb 130: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/004_smtpd.patch.sig">
1.5 tj 131: A source code patch exists which remedies this problem.</a>
132: <p>
133:
1.25 tb 134: <li id="p005_wsfont">
1.6 tj 135: <font color="#009000">
136: <strong>005: RELIABILITY FIX: September 17, 2016</strong></font>
137: <i>All architectures</i>
138: <br>
139: Limit the number of wscons fonts that can be loaded into the kernel.
140: <br>
1.14 tb 141: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/005_wsfont.patch.sig">
1.6 tj 142: A source code patch exists which remedies this problem.</a>
143: <p>
144:
1.25 tb 145: <li id="p006_iked">
1.7 benno 146: <font color="#009000">
147: <strong>006: RELIABILITY FIX: September 17, 2016</strong></font>
148: <i>All architectures</i>
149: <br>
150: During parsing of the iked(8) configuration, a variable is set to 0
151: by mistake, disabling Pre-Shared Key authentication.
152: <br>
1.14 tb 153: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/006_iked.patch.sig">
1.7 benno 154: A source code patch exists which remedies this problem.</a>
155: <p>
156:
1.25 tb 157: <li id="p007_libcrypto">
1.8 tj 158: <font color="#009000">
159: <strong>007: RELIABILITY FIX: September 22, 2016</strong></font>
160: <i>All architectures</i>
161: <br>
162: Revert change that cleans up the EVP cipher context in EVP_EncryptFinal()
163: and EVP_DecryptFinal(). Some software relies on the previous behaviour.
164: <br>
1.14 tb 165: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/007_libcrypto.patch.sig">
1.8 tj 166: A source code patch exists which remedies this problem.</a>
167: <p>
168:
1.25 tb 169: <li id="p008_libssl">
1.8 tj 170: <font color="#009000">
171: <strong>008: RELIABILITY FIX: September 22, 2016</strong></font>
172: <i>All architectures</i>
173: <br>
174: Avoid unbounded memory growth in libssl, which can be triggered by a TLS
175: client repeatedly renegotiating and sending OCSP Status Request TLS extensions.
176: <br>
1.14 tb 177: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/008_libssl.patch.sig">
1.8 tj 178: A source code patch exists which remedies this problem.</a>
179: <p>
180:
1.25 tb 181: <li id="p009_libssl">
1.8 tj 182: <font color="#009000">
183: <strong>009: SECURITY FIX: September 22, 2016</strong></font>
184: <i>All architectures</i>
185: <br>
186: Avoid falling back to a weak digest for (EC)DH when using SNI with libssl.
187: <br>
1.14 tb 188: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/009_libssl.patch.sig">
1.8 tj 189: A source code patch exists which remedies this problem.</a>
190: <p>
191:
1.25 tb 192: <li id="p010_smtpd">
1.9 tj 193: <font color="#009000">
194: <strong>010: RELIABILITY FIX: October 3, 2016</strong></font>
195: <i>All architectures</i>
196: <br>
197: A bug in the smtp session logic can lead to a server crash.
198: <br>
1.14 tb 199: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/010_smtpd.patch.sig">
1.9 tj 200: A source code patch exists which remedies this problem.</a>
201: <p>
202:
1.25 tb 203: <li id="p011_xorg_libs">
1.10 tj 204: <font color="#009000">
205: <strong>011: SECURITY FIX: October 4, 2016</strong></font>
206: <i>All architectures</i>
207: <br>
208: Fix a number of issues in the way various X client libraries handle
209: server responses.
210: <br>
1.14 tb 211: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/011_xorg_libs.patch.sig">
1.10 tj 212: A source code patch exists which remedies this problem.</a>
213: <p>
214:
1.25 tb 215: <li id="p012_amap">
1.11 deraadt 216: <font color="#009000">
1.12 tj 217: <strong>012: RELIABILITY FIX: October 8, 2016</strong></font>
1.11 deraadt 218: <i>All architectures</i>
219: <br>
220: Allocation of an amap with at least 131072 slots causes an integer overflow
221: that leads to an infinite loop.
222: <br>
1.15 tj 223: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/012_amap.patch.sig">
1.12 tj 224: A source code patch exists which remedies this problem.</a>
225: <p>
226:
1.25 tb 227: <li id="p013_ssh_kexinit">
1.12 tj 228: <font color="#009000">
229: <strong>013: RELIABILITY FIX: October 10, 2016</strong></font>
230: <i>All architectures</i>
231: <br>
232: A protocol parsing bug in sshd can lead to unauthenticated memory
233: and CPU consumption.
234: <br>
235: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/013_ssh_kexinit.patch.sig">
1.11 deraadt 236: A source code patch exists which remedies this problem.</a>
237: <p>
238:
1.25 tb 239: <li id="p014_smtpd.patch">
1.13 tj 240: <font color="#009000">
241: <strong>014: RELIABILITY FIX: October 13, 2016</strong></font>
242: <i>All architectures</i>
243: <br>
244: A logic issue in smtpd's header parsing can cause SMTP sessions to hang.
245: <br>
246: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/014_smtpd.patch.sig">
247: A source code patch exists which remedies this problem.</a>
248: <p>
249:
1.25 tb 250: <li id="p015_libssl.patch">
1.16 tj 251: <font color="#009000">
252: <strong>015: RELIABILITY FIX: November 5, 2016</strong></font>
253: <i>All architectures</i>
254: <br>
255: Avoid continual processing of an unlimited number of TLS records.
256: <br>
257: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/015_libssl.patch.sig">
258: A source code patch exists which remedies this problem.</a>
259: <p>
260:
1.25 tb 261: <li id="p016_libcrypto.patch">
1.17 tj 262: <font color="#009000">
263: <strong>016: SECURITY FIX: January 5, 2017</strong></font>
264: <i>All architectures</i>
265: <br>
266: Avoid possible side-channel leak of ECDSA private keys when signing.
267: <br>
268: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/016_libcrypto.patch.sig">
269: A source code patch exists which remedies this problem.</a>
270: <p>
271:
1.25 tb 272: <li id="p017_httpd.patch">
1.18 tb 273: <font color="#009000">
274: <strong>017: RELIABILITY FIX: January 31, 2017</strong></font>
275: <i>All architectures</i>
276: <br>
277: A bug in the processing of range headers in httpd can lead to memory
278: exhaustion and a crash of httpd. This patch disables range header
279: processing.
280: <br>
281: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/017_httpd.patch.sig">
282: A source code patch exists which remedies this problem.</a>
283: <p>
284:
1.25 tb 285: <li id="p018_net80211.patch">
1.19 tj 286: <font color="#009000">
287: <strong>018: SECURITY FIX: March 1, 2017</strong></font>
288: <i>All architectures</i>
289: <br>
1.20 stsp 290: WiFi clients using WPA1 or WPA2 are vulnerable to a man-in-the-middle attack
1.21 stsp 291: by rogue access points.
1.19 tj 292: <br>
293: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/018_net80211.patch.sig">
294: A source code patch exists which remedies this problem.</a>
295: <p>
296:
1.25 tb 297: <li id="p019_pf.patch">
1.22 tj 298: <font color="#009000">
299: <strong>019: RELIABILITY FIX: March 9, 2017</strong></font>
300: <i>All architectures</i>
301: <br>
302: Prevent integer overflow in PF when calculating the adaptive timeout,
303: causing spuriously expired states under pressure.
304: <br>
305: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/019_pf.patch.sig">
306: A source code patch exists which remedies this problem.</a>
307: <p>
308:
1.25 tb 309: <li id="p020_exec_elf.patch">
1.23 tj 310: <font color="#009000">
311: <strong>020: SECURITY FIX: March 20, 2017</strong></font>
312: <i>All architectures</i>
313: <br>
314: ELF auxiliary vector storage leaks piece of kernel stack.
315: <br>
316: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/020_exec_elf.patch.sig">
317: A source code patch exists which remedies this problem.</a>
318: <p>
319:
1.26 tj 320: <li id="p021_softraid_concat">
321: <font color="#009000">
322: <strong>021: RELIABILITY FIX: May 2, 2017</strong></font>
323: <i>All architectures</i>
324: <br>
325: softraid was unable to create usable concat volumes because
326: it always set the size of the volume to zero sectors.
327: <br>
328: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/021_softraid_concat.patch.sig">
329: A source code patch exists which remedies this problem.</a>
330: <p>
331:
1.27 tj 332: <li id="p022_libssl">
333: <font color="#009000">
334: <strong>022: RELIABILITY FIX: May 8, 2017</strong></font>
335: <i>All architectures</i>
336: <br>
337: Incorrect DTLS cookie handling can result in a NULL pointer dereference.
338: <br>
339: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/022_libssl.patch.sig">
340: A source code patch exists which remedies this problem.</a>
341: <p>
342:
1.28 tj 343: <li id="p023_freetype">
344: <font color="#009000">
1.29 tj 345: <strong>023: SECURITY FIX: May 13, 2017</strong></font>
1.28 tj 346: <i>All architectures</i>
347: <br>
348: Heap-based buffer overflows in freetype can result in out-of-bounds writes.
349: <br>
350: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/023_freetype.patch.sig">
351: A source code patch exists which remedies this problem.</a>
352: <p>
353:
1.30 tj 354: <li id="p024_exec_subr">
355: <font color="#009000">
356: <strong>024: SECURITY FIX: May 19, 2017</strong></font>
357: <i>All architectures</i>
358: <br>
359: An additional mitigation is added by placing a gap of 1 MB between the
360: stack and mmap spaces.
361: <br>
362: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/024_exec_subr.patch.sig">
363: A source code patch exists which remedies this problem.</a>
364: <p>
365:
1.31 tj 366: <li id="p025_icmp_opts">
367: <font color="#009000">
368: <strong>025: RELIABILITY FIX: May 22, 2017</strong></font>
369: <i>All architectures</i>
370: <br>
371: The kernel could leak memory when processing ICMP packets with IP options.
372: Note that pf blocks such packets by default.
373: <br>
374: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/025_icmp_opts.patch.sig">
375: A source code patch exists which remedies this problem.</a>
376: <p>
377:
1.32 tj 378: <li id="p026_perl">
379: <font color="#009000">
380: <strong>026: SECURITY FIX: June 4, 2017</strong></font>
381: <i>All architectures</i>
382: <br>
383: A race condition exists in the File::Path perl module.
384: <br>
385: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/026_perl.patch.sig">
386: A source code patch exists which remedies this problem.</a>
387: <p>
388:
1.33 tj 389: <li id="p027_sti">
390: <font color="#009000">
391: <strong>027: SECURITY FIX: June 12, 2017</strong></font>
392: <i>hppa</i>
393: <br>
394: An integer overflow exists in two range checks of the sti(4) display driver.
395: <br>
396: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/027_sti.patch.sig">
397: A source code patch exists which remedies this problem.</a>
398: <p>
399:
400: <li id="p028_wsmux">
401: <font color="#009000">
402: <strong>028: RELIABILITY FIX: June 12, 2017</strong></font>
403: <i>All architectures</i>
404: <br>
1.34 jsg 405: An unprivileged user can cause a kernel crash.
1.33 tj 406: <br>
407: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/028_wsmux.patch.sig">
408: A source code patch exists which remedies this problem.</a>
409: <p>
410:
1.36 tj 411: <li id="p029_sigio">
412: <font color="#009000">
413: <strong>029: RELIABILITY FIX: August 3, 2017</strong></font>
414: <i>All architectures</i>
415: <br>
416: A SIGIO-related use-after-free can occur in two drivers.
417: <br>
418: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/029_sigio.patch.sig">
419: A source code patch exists which remedies this problem.</a>
420: <p>
421:
422: <li id="p030_sendsyslog">
423: <font color="#009000">
424: <strong>030: RELIABILITY FIX: August 3, 2017</strong></font>
425: <i>All architectures</i>
426: <br>
427: A missing length check in sendsyslog() may result in a kernel panic.
428: <br>
429: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/030_sendsyslog.patch.sig">
430: A source code patch exists which remedies this problem.</a>
431: <p>
432:
433: <li id="p031_fuse">
434: <font color="#009000">
435: <strong>031: SECURITY FIX: August 3, 2017</strong></font>
436: <i>All architectures</i>
437: <br>
438: An out-of-bound read in vfs_getcwd_scandir() (mainly used for FUSE)
439: may result in a kernel panic or info leak.
440: <br>
441: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/031_fuse.patch.sig">
442: A source code patch exists which remedies this problem.</a>
443: <p>
444:
445: <li id="p032_recv">
446: <font color="#009000">
447: <strong>032: SECURITY FIX: August 3, 2017</strong></font>
448: <i>All architectures</i>
449: <br>
450: An alignment issue in recv() may result in an info leak via ktrace().
451: <br>
452: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/032_recv.patch.sig">
453: A source code patch exists which remedies this problem.</a>
454: <p>
455:
456: <li id="p033_tcp_usrreq">
457: <font color="#009000">
458: <strong>033: SECURITY FIX: August 3, 2017</strong></font>
459: <i>All architectures</i>
460: <br>
461: With an invalid address family, tcp_usrreq() may take an unintended code path.
462: <br>
463: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/033_tcp_usrreq.patch.sig">
464: A source code patch exists which remedies this problem.</a>
465: <p>
466:
467: <li id="p034_sockaddr">
468: <font color="#009000">
469: <strong>034: SECURITY FIX: August 3, 2017</strong></font>
470: <i>All architectures</i>
471: <br>
472: Missing socket address validation from userland may result in an info leak.
473: <br>
474: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/034_sockaddr.patch.sig">
475: A source code patch exists which remedies this problem.</a>
476: <p>
477:
478: <li id="p035_ptrace">
479: <font color="#009000">
480: <strong>035: SECURITY FIX: August 3, 2017</strong></font>
481: <i>All architectures</i>
482: <br>
483: An uninitialized variable in ptrace() may result in an info leak.
484: <br>
485: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/035_ptrace.patch.sig">
486: A source code patch exists which remedies this problem.</a>
487: <p>
488:
489: <li id="p036_fcntl">
490: <font color="#009000">
491: <strong>036: SECURITY FIX: August 3, 2017</strong></font>
492: <i>All architectures</i>
493: <br>
494: An uninitialized variable in fcntl() may result in an info leak.
495: <br>
496: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/036_fcntl.patch.sig">
497: A source code patch exists which remedies this problem.</a>
498: <p>
499:
500: <li id="p037_wsdisplay">
501: <font color="#009000">
502: <strong>037: RELIABILITY FIX: August 3, 2017</strong></font>
503: <i>All architectures</i>
504: <br>
505: An integer overflow in wsdisplay_cfg_ioctl() may result in an out-of-bounds
506: read.
507: <br>
508: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/037_wsdisplay.patch.sig">
509: A source code patch exists which remedies this problem.</a>
510: <p>
511:
512: <li id="p038_sosplice">
513: <font color="#009000">
514: <strong>038: SECURITY FIX: August 3, 2017</strong></font>
515: <i>All architectures</i>
516: <br>
517: A race condition may result in a kernel memory leak.
518: <br>
519: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/038_sosplice.patch.sig">
520: A source code patch exists which remedies this problem.</a>
521: <p>
522:
523: <li id="p039_ieee80211">
524: <font color="#009000">
525: <strong>039: SECURITY FIX: August 3, 2017</strong></font>
526: <i>All architectures</i>
527: <br>
528: An out of bounds read could occur during processing of EAPOL frames in
529: the wireless stack. Information from kernel memory could be leaked to
530: root in userland via an ieee80211(9) ioctl.
531: <br>
532: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/039_ieee80211.patch.sig">
533: A source code patch exists which remedies this problem.</a>
534: <p>
535:
1.37 tj 536: <li id="p040_smap">
537: <font color="#009000">
538: <strong>040: SECURITY FIX: August 26, 2017</strong></font>
539: <i>amd64 and i386</i>
540: <br>
541: SMAP enforcement could be bypassed by userland code.
542: <br>
543: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/040_smap.patch.sig">
544: A source code patch exists which remedies this problem.</a>
545: <p>
546:
1.38 ! tj 547: <li id="p041_net80211_replay">
! 548: <font color="#009000">
! 549: <strong>041: SECURITY FIX: August 30, 2017</strong></font>
! 550: <i>All architectures</i>
! 551: <br>
! 552: State transition errors could cause reinstallation of old WPA keys.
! 553: <br>
! 554: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/041_net80211_replay.patch.sig">
! 555: A source code patch exists which remedies this problem.</a>
! 556: <p>
! 557:
1.1 deraadt 558: </ul>
559:
560: <hr>
561:
562: </body>
563: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to errata60.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www