Annotation of www/errata67.html, Revision 1.38
1.1 deraadt 1: <!doctype html>
2: <html lang=en id=errata>
3: <meta charset=utf-8>
4:
5: <title>OpenBSD 6.7 Errata</title>
6: <meta name="description" content="the OpenBSD errata page">
7: <meta name="viewport" content="width=device-width, initial-scale=1">
8: <link rel="stylesheet" type="text/css" href="openbsd.css">
1.2 schwarze 9: <link rel="canonical" href="https://www.openbsd.org/errata67.html">
1.1 deraadt 10:
11: <!--
12: IMPORTANT REMINDER
13: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
14: -->
15:
16: <h2 id=OpenBSD>
17: <a href="index.html">
18: <i>Open</i><b>BSD</b></a>
19: 6.7 Errata
20: </h2>
21: <hr>
22:
23: For errata on a certain release, click below:<br>
1.2 schwarze 24: <a href="errata20.html">2.0</a>,
1.1 deraadt 25: <a href="errata21.html">2.1</a>,
26: <a href="errata22.html">2.2</a>,
27: <a href="errata23.html">2.3</a>,
28: <a href="errata24.html">2.4</a>,
29: <a href="errata25.html">2.5</a>,
30: <a href="errata26.html">2.6</a>,
31: <a href="errata27.html">2.7</a>,
32: <a href="errata28.html">2.8</a>,
33: <a href="errata29.html">2.9</a>,
34: <a href="errata30.html">3.0</a>,
35: <a href="errata31.html">3.1</a>,
36: <a href="errata32.html">3.2</a>,
37: <a href="errata33.html">3.3</a>,
38: <a href="errata34.html">3.4</a>,
39: <a href="errata35.html">3.5</a>,
1.2 schwarze 40: <br>
1.1 deraadt 41: <a href="errata36.html">3.6</a>,
42: <a href="errata37.html">3.7</a>,
43: <a href="errata38.html">3.8</a>,
44: <a href="errata39.html">3.9</a>,
45: <a href="errata40.html">4.0</a>,
46: <a href="errata41.html">4.1</a>,
47: <a href="errata42.html">4.2</a>,
48: <a href="errata43.html">4.3</a>,
49: <a href="errata44.html">4.4</a>,
50: <a href="errata45.html">4.5</a>,
51: <a href="errata46.html">4.6</a>,
52: <a href="errata47.html">4.7</a>,
53: <a href="errata48.html">4.8</a>,
54: <a href="errata49.html">4.9</a>,
55: <a href="errata50.html">5.0</a>,
56: <a href="errata51.html">5.1</a>,
1.2 schwarze 57: <br>
1.1 deraadt 58: <a href="errata52.html">5.2</a>,
59: <a href="errata53.html">5.3</a>,
60: <a href="errata54.html">5.4</a>,
61: <a href="errata55.html">5.5</a>,
62: <a href="errata56.html">5.6</a>,
63: <a href="errata57.html">5.7</a>,
64: <a href="errata58.html">5.8</a>,
65: <a href="errata59.html">5.9</a>,
66: <a href="errata60.html">6.0</a>,
67: <a href="errata61.html">6.1</a>,
68: <a href="errata62.html">6.2</a>,
69: <a href="errata63.html">6.3</a>,
70: <a href="errata64.html">6.4</a>,
71: <a href="errata65.html">6.5</a>,
1.24 deraadt 72: <a href="errata66.html">6.6</a>,
1.38 ! deraadt 73: <a href="errata68.html">6.8</a>,
! 74: <a href="errata69.html">6.9</a>.
1.1 deraadt 75: <hr>
76:
77: <p>
78: Patches for the OpenBSD base system are distributed as unified diffs.
79: Each patch is cryptographically signed with the
80: <a href="https://man.openbsd.org/OpenBSD-6.7/signify.1">signify(1)</a> tool and contains
81: usage instructions.
82: All the following patches are also available in one
83: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7.tar.gz">tar.gz file</a>
84: for convenience.
85:
86: <p>
87: Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
88: utility can be used to apply binary updates on the following architectures:
89: amd64, i386, arm64.
90:
91: <p>
92: Patches for supported releases are also incorporated into the
93: <a href="stable.html">-stable branch</a>, which is maintained for one year
94: after release.
95:
96: <hr>
97:
98: <ul>
99:
1.3 tj 100: <li id="p001_wscons">
101: <strong>001: SECURITY FIX: May 19, 2020</strong>
102: <i>All architectures</i>
103: <br>
104: An out-of-bounds index access in wscons(4) can cause a kernel crash.
105: <br>
106: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/001_wscons.patch.sig">
107: A source code patch exists which remedies this problem.</a>
108: <p>
1.1 deraadt 109:
1.5 tj 110: <li id="p002_rpki">
1.4 tj 111: <strong>002: RELIABILITY FIX: May 22, 2020</strong>
112: <i>All architectures</i>
113: <br>
114: rpki-client could hang because of an improper waitpid idiom for rsync
115: processes.
116: <br>
1.5 tj 117: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/002_rpki.patch.sig">
1.4 tj 118: A source code patch exists which remedies this problem.</a>
119: <p>
120:
1.5 tj 121: <li id="p003_ssh">
1.4 tj 122: <strong>003: SECURITY FIX: May 22, 2020</strong>
123: <i>All architectures</i>
124: <br>
125: When attempting to download resident keys from a FIDO token that does
126: not require a password/PIN, ssh-keygen would crash with a NULL
127: dereference.
128: <br>
1.5 tj 129: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/003_ssh.patch.sig">
1.4 tj 130: A source code patch exists which remedies this problem.</a>
131: <p>
132:
1.6 tj 133: <li id="p004_libssl">
134: <strong>004: RELIABILITY FIX: May 22, 2020</strong>
135: <i>All architectures</i>
136: <br>
137: A TLS client with peer verification disabled may crash when contacting a
138: server that sends an empty certificate list.
139: <br>
140: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/004_libssl.patch.sig">
141: A source code patch exists which remedies this problem.</a>
142: <p>
143:
144: <li id="p005_unbound">
145: <strong>005: SECURITY FIX: May 22, 2020</strong>
146: <i>All architectures</i>
147: <br>
148: Specially crafted queries may crash unbound and unwind.
149: Both can be tricked into amplifying an incoming query.
150: <br>
151: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/005_unbound.patch.sig">
152: A source code patch exists which remedies this problem.</a>
153: <p>
154:
1.7 tj 155: <li id="p006_smtpd_sockaddr">
156: <strong>006: SECURITY FIX: May 25, 2020</strong>
157: <i>All architectures</i>
158: <br>
159: Incorrect use of getpeername(2) storage for outgoing IPv6 connections
160: corrupts stack memory. The nature of the corruption and existing
161: mitigations appear to make this difficult to effectively target.
162: <br>
163: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/006_smtpd_sockaddr.patch.sig">
164: A source code patch exists which remedies this problem.</a>
165: <p>
166:
1.8 tj 167: <li id="p007_perl">
168: <strong>007: SECURITY FIX: June 1, 2020</strong>
169: <i>All architectures</i>
170: <br>
171: Several problems in Perl's regular expression compiler could lead to
172: corruption of the intermediate language state of a compiled regular
173: expression.
174: <br>
175: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/007_perl.patch.sig">
176: A source code patch exists which remedies this problem.</a>
177: <p>
178:
1.9 tj 179: <li id="p008_hid">
180: <strong>008: SECURITY FIX: June 5, 2020</strong>
181: <i>All architectures</i>
182: <br>
183: Malicious HID descriptors could be misparsed.
184: <br>
185: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/008_hid.patch.sig">
186: A source code patch exists which remedies this problem.</a>
187: <p>
188:
1.10 tj 189: <li id="p009_asr">
190: <strong>009: RELIABILITY FIX: June 8, 2020</strong>
191: <i>All architectures</i>
192: <br>
193: libc's resolver could get into a corrupted state.
194: <br>
195: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/009_asr.patch.sig">
196: A source code patch exists which remedies this problem.</a>
197: <p>
198:
1.11 tj 199: <li id="p010_x509">
200: <strong>010: RELIABILITY FIX: June 11, 2020</strong>
201: <i>All architectures</i>
202: <br>
203: libcrypto may fail to build a valid certificate chain due to
204: expired untrusted issuer certificates.
205: <br>
206: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/010_x509.patch.sig">
207: A source code patch exists which remedies this problem.</a>
208: <p>
209:
1.12 tj 210: <li id="p011_shmget">
211: <strong>011: SECURITY FIX: July 9, 2020</strong>
212: <i>All architectures</i>
213: <br>
214: shmget IPC_STAT leaked some kernel data.
215: <br>
216: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/011_shmget.patch.sig">
217: A source code patch exists which remedies this problem.</a>
218: <p>
219:
1.13 tj 220: <li id="p012_tty">
1.14 tj 221: <strong>012: RELIABILITY FIX: July 16, 2020</strong>
1.13 tj 222: <i>All architectures</i>
223: <br>
224: tty subsystem abuse can impact performance badly.
225: <br>
226: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/012_tty.patch.sig">
227: A source code patch exists which remedies this problem.</a>
228: <p>
229:
1.15 tj 230: <li id="p013_tty">
231: <strong>013: RELIABILITY FIX: July 22, 2020</strong>
232: <i>All architectures</i>
233: <br>
234: Only pty devices need reprint delays.
235: <br>
236: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/013_tty.patch.sig">
237: A source code patch exists which remedies this problem.</a>
238: <p>
239:
1.16 bluhm 240: <li id="p014_iked">
241: <strong>014: SECURITY FIX: July 27, 2020</strong>
242: <i>All architectures</i>
243: <br>
244: In iked, incorrect use of EVP_PKEY_cmp allows an authentication bypass.
245: <br>
246: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/014_iked.patch.sig">
247: A source code patch exists which remedies this problem.</a>
248: <p>
249:
250: <li id="p015_rpki">
251: <strong>015: SECURITY FIX: July 27, 2020</strong>
252: <i>All architectures</i>
253: <br>
254: In rpki-client, incorrect use of EVP_PKEY_cmp allows an authentication bypass.
255: <br>
256: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/015_rpki.patch.sig">
257: A source code patch exists which remedies this problem.</a>
258: <p>
259:
1.17 tj 260: <li id="p016_ximcp">
261: <strong>016: SECURITY FIX: July 31, 2020</strong>
262: <i>All architectures</i>
263: <br>
264: Malformed messages can cause heap corruption in the X Input Method
265: client implementation in libX11.
266: <br>
267: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/016_ximcp.patch.sig">
268: A source code patch exists which remedies this problem.</a>
269: <p>
270:
271: <li id="p017_dix">
272: <strong>017: SECURITY FIX: July 31, 2020</strong>
273: <i>All architectures</i>
274: <br>
275: Pixmaps inside the xserver were an info leak.
276: <br>
277: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/017_dix.patch.sig">
278: A source code patch exists which remedies this problem.</a>
279: <p>
280:
1.18 tj 281: <li id="p018_ximcp">
282: <strong>018: RELIABILITY FIX: August 7, 2020</strong>
283: <i>All architectures</i>
284: <br>
285: The recent security errata 016 broke X11 input methods.
286: <br>
287: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/018_ximcp.patch.sig">
288: A source code patch exists which remedies this problem.</a>
289: <p>
290:
1.19 tj 291: <li id="p019_libssl">
292: <strong>019: RELIABILITY FIX: August 11, 2020</strong>
293: <i>All architectures</i>
294: <br>
295: The TLSv1.3 client could hang, crash, leak memory or not interoperate with
296: some TLSv1.3 servers.
297: <br>
298: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/019_libssl.patch.sig">
299: A source code patch exists which remedies this problem.</a>
300: <p>
301:
1.20 tj 302: <li id="p020_libssl">
303: <strong>020: RELIABILITY FIX: August 18, 2020</strong>
304: <i>All architectures</i>
305: <br>
306: The previous errata patch 019 broke bidirectional SSL_shutdown.
307: <br>
1.21 tj 308: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/020_libssl.patch.sig">
1.20 tj 309: A source code patch exists which remedies this problem.</a>
310: <p>
311:
1.22 tj 312: <li id="p021_xinitom">
313: <strong>021: SECURITY FIX: August 25, 2020</strong>
314: <i>All architectures</i>
315: <br>
316: An integer overflow in libX11 could lead to a double free.
317: Additionally fix a regression in ximcp.
318: <br>
319: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/021_xinitom.patch.sig">
320: A source code patch exists which remedies this problem.</a>
1.29 tb 321: <p>
1.22 tj 322:
323: <li id="p022_xserverlen">
324: <strong>022: SECURITY FIX: August 25, 2020</strong>
325: <i>All architectures</i>
326: <br>
327: Various X server extensions had deficient input validation.
328: <br>
329: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/022_xserverlen.patch.sig">
330: A source code patch exists which remedies this problem.</a>
331: <p>
332:
1.23 tj 333: <li id="p023_amdgpu">
334: <strong>023: SECURITY FIX: September 5, 2020</strong>
335: <i>amd64, arm64</i>
336: <br>
337: A buffer overflow was discovered in an amdgpu ioctl.
338: <br>
339: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/023_amdgpu.patch.sig">
340: A source code patch exists which remedies this problem.</a>
341: <p>
342:
1.25 tj 343: <li id="p024_mmap">
344: <strong>024: RELIABILITY FIX: October 6, 2020</strong>
345: <i>All architectures</i>
346: <br>
347: mmap can exhaust kernel memory for PROT_NONE MAP_SHARED mappings.
348: <br>
349: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/024_mmap.patch.sig">
350: A source code patch exists which remedies this problem.</a>
351: <p>
352:
1.26 tj 353: <li id="p025_bgpd">
354: <strong>025: RELIABILITY FIX: October 29, 2020</strong>
355: <i>All architectures</i>
356: <br>
357: In bgpd, the roa-set parser could leak memory.
358: <br>
359: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/025_bgpd.patch.sig">
360: A source code patch exists which remedies this problem.</a>
361: <p>
362:
1.27 tb 363: <li id="p026_icmp6">
364: <strong>026: SECURITY FIX: October 29, 2020</strong>
365: <i>All architectures</i>
366: <br>
367: When generating the ICMP6 response to an IPv6 packet, the kernel
368: could use mbuf memory after freeing it.
369: <br>
370: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/026_icmp6.patch.sig">
371: A source code patch exists which remedies this problem.</a>
372: <p>
373:
1.28 tb 374: <li id="p027_tmux">
375: <strong>027: SECURITY FIX: October 29, 2020</strong>
376: <i>All architectures</i>
377: <br>
378: tmux has a stack overflow in CSI parsing.
379: <br>
380: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/027_tmux.patch.sig">
381: A source code patch exists which remedies this problem.</a>
1.29 tb 382: <p>
383:
384: <li id="p028_unwind">
385: <strong>028: RELIABILITY FIX: November 10, 2020</strong>
386: <i>All architectures</i>
387: <br>
388: unwind fails to process large DNS replies.
389: <br>
390: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/028_unwind.patch.sig">
391: A source code patch exists which remedies this problem.</a>
392: <p>
393:
394: <li id="p029_rpki">
395: <strong>029: RELIABILITY FIX: November 10, 2020</strong>
396: <i>All architectures</i>
397: <br>
398: rpki-client incorrectly checks the manifest validity interval.
399: <br>
400: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/029_rpki.patch.sig">
401: A source code patch exists which remedies this problem.</a>
402: <p>
1.28 tb 403:
1.30 tb 404: <li id="p030_xmaplen">
405: <strong>030: SECURITY FIX: December 1, 2020</strong>
406: <i>All architectures</i>
407: <br>
408: Multiple input validation failures in the X server XKB extension can lead
409: to out of bounds memory accesses for authorized clients.
410: <br>
411: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/030_xmaplen.patch.sig">
412: A source code patch exists which remedies this problem.</a>
413: <p>
414:
1.31 tb 415: <li id="p031_asn1">
416: <strong>031: SECURITY FIX: December 8, 2020</strong>
417: <i>All architectures</i>
418: <br>
419: Malformed ASN.1 in a certificate revocation list or a timestamp
420: response token can lead to a NULL pointer dereference.
421: <br>
422: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/031_asn1.patch.sig">
423: A source code patch exists which remedies this problem.</a>
424: <p>
425:
426: <li id="p032_exit">
427: <strong>032: RELIABILITY FIX: December 8, 2020</strong>
428: <i>All architectures</i>
429: <br>
430: Process exit in multithreaded programs could result in the wrong exit
431: code being reported.
432: <br>
433: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/032_exit.patch.sig">
434: A source code patch exists which remedies this problem.</a>
435: <p>
436:
1.32 tb 437: <li id="p033_smtpd">
438: <strong>033: RELIABILITY FIX: December 24, 2020</strong>
439: <i>All architectures</i>
440: <br>
441: smtpd's filter state machine can prematurely release resources
442: leading to a crash.
443: <br>
444: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/033_smtpd.patch.sig">
445: A source code patch exists which remedies this problem.</a>
446: <p>
447:
1.33 benno 448: <li id="p034_nd6">
449: <strong>034: RELIABILITY FIX: January 11, 2021</strong>
450: <i>All architectures</i>
451: <br>
452: When an NDP entry is invalidated the associated layer 2 address
453: is not invalidated.
454: <br>
455: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/034_nd6.patch.sig">
456: A source code patch exists which remedies this problem.</a>
457: <p>
458:
1.34 bluhm 459: <li id="p035_pffrag">
1.35 patrick 460: <strong>035: SECURITY FIX: February 24, 2021</strong>
1.34 bluhm 461: <i>All architectures</i>
462: <br>
463: A sequence of overlapping IPv4 fragments could crash the kernel in
464: pf due to an assertion.
465: <br>
466: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/035_pffrag.patch.sig">
467: A source code patch exists which remedies this problem.</a>
468: <p>
469:
1.36 bluhm 470: <li id="p036_sshagent">
471: <strong>036: SECURITY FIX: March 4, 2021</strong>
472: <i>All architectures</i>
473: <br>
474: Double free in ssh-agent(1)
475: <br>
476: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/036_sshagent.patch.sig">
477: A source code patch exists which remedies this problem.</a>
478: <p>
479:
1.37 bluhm 480: <li id="p037_npppd">
481: <strong>037: SECURITY FIX: March 9, 2021</strong>
482: <i>All architectures</i>
483: <br>
484: npppd PPTP protocol handler can cause heap over-read leading to a crash.
485: <br>
486: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.7/common/037_npppd.patch.sig">
487: A source code patch exists which remedies this problem.</a>
488: <p>
489:
1.1 deraadt 490: </ul>
491:
492: <hr>