Annotation of www/errata66.html, Revision 1.43
1.1 deraadt 1: <!doctype html>
2: <html lang=en id=errata>
3: <meta charset=utf-8>
4:
5: <title>OpenBSD 6.6 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">
9: <link rel="canonical" href="https://www.openbsd.org/errata66.html">
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.6 Errata
20: </h2>
21: <hr>
22:
23: For errata on a certain release, click below:<br>
1.21 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.21 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.21 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>,
1.22 deraadt 71: <a href="errata65.html">6.5</a>,
1.39 deraadt 72: <a href="errata67.html">6.7</a>,
1.41 deraadt 73: <a href="errata68.html">6.8</a>,
1.42 tj 74: <br>
1.43 ! deraadt 75: <a href="errata69.html">6.9</a>,
! 76: <a href="errata70.html">7.0</a>.
1.1 deraadt 77: <hr>
78:
79: <p>
80: Patches for the OpenBSD base system are distributed as unified diffs.
81: Each patch is cryptographically signed with the
82: <a href="https://man.openbsd.org/OpenBSD-6.6/signify.1">signify(1)</a> tool and contains
83: usage instructions.
84: All the following patches are also available in one
85: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6.tar.gz">tar.gz file</a>
86: for convenience.
87:
88: <p>
89: Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
90: utility can be used to apply binary updates on the following architectures:
91: amd64, i386, arm64.
92:
93: <p>
94: Patches for supported releases are also incorporated into the
1.40 tj 95: <a href="stable.html">-stable branch</a>.
1.1 deraadt 96:
97: <hr>
98:
99: <ul>
100:
1.2 tj 101: <li id="p001_bpf">
102: <strong>001: RELIABILITY FIX: October 28, 2019</strong>
103: <i>All architectures</i>
104: <br>
105: bpf(4) has a race condition during device removal.
106: <br>
107: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/001_bpf.patch.sig">
108: A source code patch exists which remedies this problem.</a>
109: <p>
110:
111: <li id="p002_ber">
112: <strong>002: RELIABILITY FIX: October 28, 2019</strong>
113: <i>All architectures</i>
114: <br>
115: Various third party applications may crash due to symbol collision.
116: <br>
117: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/002_ber.patch.sig">
118: A source code patch exists which remedies this problem.</a>
119: <p>
1.1 deraadt 120:
1.4 tj 121: <li id="p003_bgpd">
122: <strong>003: RELIABILITY FIX: October 31, 2019</strong>
123: <i>All architectures</i>
124: <br>
125: bgpd(8) can crash on nexthop changes or during startup in certain
126: configurations.
127: <br>
128: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/003_bgpd.patch.sig">
129: A source code patch exists which remedies this problem.</a>
130: <p>
131:
1.5 tj 132: <li id="p004_net80211">
133: <strong>004: RELIABILITY FIX: November 16, 2019</strong>
134: <i>All architectures</i>
135: <br>
136: The kernel could crash due to a NULL pointer dereference in net80211.
137: <br>
138: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/004_net80211.patch.sig">
139: A source code patch exists which remedies this problem.</a>
140: <p>
141:
142: <li id="p005_sysupgrade">
143: <strong>005: RELIABILITY FIX: November 16, 2019</strong>
144: <i>All architectures</i>
145: <br>
146: A new kernel may require newer firmware images when using sysupgrade.
147: <br>
148: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/005_sysupgrade.patch.sig">
149: A source code patch exists which remedies this problem.</a>
150: <p>
151:
152: <li id="p006_ifioctl">
153: <strong>006: SECURITY FIX: November 16, 2019</strong>
154: <i>All architectures</i>
155: <br>
156: A regular user could change some network interface parameters due
157: to missing checks in the ioctl(2) system call.
158: <br>
159: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/006_ifioctl.patch.sig">
160: A source code patch exists which remedies this problem.</a>
161: <p>
162:
1.6 tj 163: <li id="p007_inteldrm">
164: <strong>007: SECURITY FIX: November 22, 2019</strong>
165: <i>i386 and amd64</i>
166: <br>
167: A local user could cause the system to hang by reading specific
168: registers when Intel Gen8/Gen9 graphics hardware is in a low power state.
169: A local user could perform writes to memory that should be blocked with
170: Intel Gen9 graphics hardware.
171: <br>
172: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/007_inteldrm.patch.sig">
173: A source code patch exists which remedies this problem.</a>
174: <p>
175:
176: <li id="p008_mesa">
177: <strong>008: SECURITY FIX: November 22, 2019</strong>
178: <i>All architectures</i>
179: <br>
180: Shared memory regions used by some Mesa drivers had permissions which
181: allowed others to access that memory.
182: <br>
183: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/008_mesa.patch.sig">
184: A source code patch exists which remedies this problem.</a>
185: <p>
186:
1.7 tb 187: <li id="p009_mesaxlock">
188: <strong>009: SECURITY FIX: December 4, 2019</strong>
189: <i>All architectures</i>
190: <br>
191: Environment-provided paths are used for dlopen() in mesa, resulting in
192: escalation to the auth group in xlock(1).
193: <br>
194: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/009_mesaxlock.patch.sig">
195: A source code patch exists which remedies this problem.</a>
196: <p>
197:
198: <li id="p010_libcauth">
199: <strong>010: SECURITY FIX: December 4, 2019</strong>
200: <i>All architectures</i>
201: <br>
202: libc's authentication layer performed insufficient username validation.
203: <br>
204: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/010_libcauth.patch.sig">
205: A source code patch exists which remedies this problem.</a>
206: <p>
207:
208: <li id="p011_xenodm">
209: <strong>011: SECURITY FIX: December 4, 2019</strong>
210: <i>All architectures</i>
211: <br>
212: xenodm uses the libc authentication layer incorrectly.
213: <br>
214: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/011_xenodm.patch.sig">
215: A source code patch exists which remedies this problem.</a>
216: <p>
217:
1.8 tj 218: <li id="p012_suauth">
219: <strong>012: SECURITY FIX: December 8, 2019</strong>
220: <i>All architectures</i>
221: <br>
222: A user can log in with a different user's login class.
223: <br>
224: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/012_suauth.patch.sig">
225: A source code patch exists which remedies this problem.</a>
226: <p>
227:
1.9 tj 228: <li id="p013_ldso">
229: <strong>013: SECURITY FIX: December 11, 2019</strong>
230: <i>All architectures</i>
231: <br>
232: ld.so may fail to remove the LD_LIBRARY_PATH environment variable for
233: set-user-ID and set-group-ID executables in low memory conditions.
234: <br>
235: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/013_ldso.patch.sig">
236: A source code patch exists which remedies this problem.</a>
237: <p>
238:
1.10 tj 239: <li id="p014_eret">
240: <strong>014: SECURITY FIX: December 18, 2019</strong>
241: <i>arm64</i>
242: <br>
243: ARM64 CPUs speculatively execute instructions after ERET.
244: <br>
245: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/014_eret.patch.sig">
246: A source code patch exists which remedies this problem.</a>
247: <p>
248:
1.11 tj 249: <li id="p015_ftp">
250: <strong>015: SECURITY FIX: December 20, 2019</strong>
251: <i>All architectures</i>
252: <br>
253: ftp(1) will follow remote redirects to local files.
254: <br>
255: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/015_ftp.patch.sig">
256: A source code patch exists which remedies this problem.</a>
257: <p>
258:
259: <li id="p016_ripd">
260: <strong>016: SECURITY FIX: December 20, 2019</strong>
261: <i>All architectures</i>
262: <br>
263: ripd(8) fails to validate authentication lengths.
264: <br>
265: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/016_ripd.patch.sig">
266: A source code patch exists which remedies this problem.</a>
267: <p>
268:
1.12 tj 269: <li id="p017_inteldrmctx">
270: <strong>017: SECURITY FIX: January 17, 2020</strong>
271: <i>i386 and amd64</i>
272: <br>
273: Execution Unit state was not cleared on context switch with Intel Gen9
274: graphics hardware.
275: <br>
276: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/017_inteldrmctx.patch.sig">
277: A source code patch exists which remedies this problem.</a>
278: <p>
279:
1.13 tj 280: <li id="p018_smtpd_tls">
281: <strong>018: RELIABILITY FIX: January 30, 2020</strong>
282: <i>All architectures</i>
283: <br>
284: smtpd can crash on opportunistic TLS downgrade, causing a denial of service.
285: <br>
286: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/018_smtpd_tls.patch.sig">
287: A source code patch exists which remedies this problem.</a>
288: <p>
289:
290: <li id="p019_smtpd_exec">
291: <strong>019: SECURITY FIX: January 30, 2020</strong>
292: <i>All architectures</i>
293: <br>
294: An incorrect check allows an attacker to trick mbox delivery into executing
295: arbitrary commands as root and lmtp delivery into executing arbitrary commands
296: as an unprivileged user.
297: <br>
298: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/019_smtpd_exec.patch.sig">
299: A source code patch exists which remedies this problem.</a>
300: <p>
301:
1.14 tj 302: <li id="p020_vmm_pvclock">
303: <strong>020: SECURITY FIX: February 17, 2020</strong>
304: <i>amd64</i>
305: <br>
306: A missing range check in the vmm pvclock allows a guest to write
307: to host memory.
308: <br>
309: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/020_vmm_pvclock.patch.sig">
310: A source code patch exists which remedies this problem.</a>
311: <p>
312:
1.15 tj 313: <li id="p021_smtpd_envelope">
314: <strong>021: SECURITY FIX: February 24, 2020</strong>
315: <i>All architectures</i>
316: <br>
317: An out of bounds read in smtpd allows an attacker to inject arbitrary
318: commands into the envelope file which are then executed as root.
319: Separately, missing privilege revocation in smtpctl allows arbitrary
320: commands to be run with the _smtpq group.
321: <br>
322: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/021_smtpd_envelope.patch.sig">
323: A source code patch exists which remedies this problem.</a>
324: <p>
1.14 tj 325:
1.16 tj 326: <li id="p022_sysctl">
327: <strong>022: RELIABILITY FIX: March 10, 2020</strong>
328: <i>All architectures</i>
329: <br>
330: Missing input validation in sysctl(2) can be used to crash the kernel.
331: <br>
332: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/022_sysctl.patch.sig">
333: A source code patch exists which remedies this problem.</a>
334: <p>
335:
1.17 tj 336: <li id="p023_sosplice">
337: <strong>023: RELIABILITY FIX: March 13, 2020</strong>
338: <i>All architectures</i>
339: <br>
340: Local outbound UDP broadcast or multicast packets sent by a spliced
341: socket can crash the kernel.
342: <br>
343: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/023_sosplice.patch.sig">
344: A source code patch exists which remedies this problem.</a>
345: <p>
346:
1.18 tj 347: <li id="p024_dhcpd">
348: <strong>024: SECURITY FIX: April 7, 2020</strong>
349: <i>All architectures</i>
350: <br>
351: dhcpd could reference freed memory after releasing a lease with an
352: unusually long uid.
353: <br>
354: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/024_dhcpd.patch.sig">
355: A source code patch exists which remedies this problem.</a>
356: <p>
357:
1.19 tj 358: <li id="p025_drm">
359: <strong>025: SECURITY FIX: April 19, 2020</strong>
360: <i>i386, amd64, arm64, loongson, macppc, sparc64</i>
361: <br>
1.20 tj 362: There was an incorrect test for root in the DRM Linux compatibility code.
1.19 tj 363: <br>
364: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/025_drm.patch.sig">
365: A source code patch exists which remedies this problem.</a>
366: <p>
367:
1.23 tj 368: <li id="p026_ospfd_lsa">
369: <strong>026: RELIABILITY FIX: May 10, 2020</strong>
370: <i>All architectures</i>
371: <br>
372: ospfd could generate corrupt OSPF Router (Type 1) LSAs in certain situations.
373: <br>
374: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/026_ospfd_lsa.patch.sig">
375: A source code patch exists which remedies this problem.</a>
376: <p>
377:
1.24 tj 378: <li id="p027_wscons">
379: <strong>027: SECURITY FIX: May 13, 2020</strong>
380: <i>All architectures</i>
381: <br>
382: An out-of-bounds index access in wscons(4) can cause a kernel crash.
383: <br>
384: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/027_wscons.patch.sig">
385: A source code patch exists which remedies this problem.</a>
386: <p>
387:
1.26 tj 388: <li id="p028_unbound">
389: <strong>028: SECURITY FIX: May 22, 2020</strong>
1.25 tj 390: <i>All architectures</i>
391: <br>
392: Specially crafted queries may crash unbound and unwind.
393: Both can be tricked into amplifying an incoming query.
394: <br>
1.26 tj 395: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/028_unbound.patch.sig">
1.25 tj 396: A source code patch exists which remedies this problem.</a>
397: <p>
398:
1.27 tj 399: <li id="p029_perl">
400: <strong>029: SECURITY FIX: June 1, 2020</strong>
401: <i>All architectures</i>
402: <br>
403: Several problems in Perl's regular expression compiler could lead to
404: corruption of the intermediate language state of a compiled regular
405: expression.
406: <br>
407: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/029_perl.patch.sig">
408: A source code patch exists which remedies this problem.</a>
409: <p>
410:
1.28 tj 411: <li id="p030_hid">
412: <strong>030: SECURITY FIX: June 5, 2020</strong>
413: <i>All architectures</i>
414: <br>
415: Malicious HID descriptors could be misparsed.
416: <br>
417: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/030_hid.patch.sig">
418: A source code patch exists which remedies this problem.</a>
419: <p>
420:
1.29 tj 421: <li id="p031_asr">
422: <strong>031: RELIABILITY FIX: June 8, 2020</strong>
423: <i>All architectures</i>
424: <br>
425: libc's resolver could get into a corrupted state.
426: <br>
427: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/031_asr.patch.sig">
428: A source code patch exists which remedies this problem.</a>
429: <p>
430:
1.30 tj 431: <li id="p032_x509">
432: <strong>032: RELIABILITY FIX: June 11, 2020</strong>
433: <i>All architectures</i>
434: <br>
435: libcrypto may fail to build a valid certificate chain due to
436: expired untrusted issuer certificates.
437: <br>
438: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/032_x509.patch.sig">
439: A source code patch exists which remedies this problem.</a>
440: <p>
441:
1.31 tj 442: <li id="p033_shmget">
443: <strong>033: SECURITY FIX: July 9, 2020</strong>
444: <i>All architectures</i>
445: <br>
446: shmget IPC_STAT leaked some kernel data.
447: <br>
448: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/033_shmget.patch.sig">
449: A source code patch exists which remedies this problem.</a>
450: <p>
451:
1.32 tj 452: <li id="p034_tty">
453: <strong>034: RELIABILITY FIX: July 16, 2020</strong>
454: <i>All architectures</i>
455: <br>
456: tty subsystem abuse can impact performance badly.
457: <br>
458: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/034_tty.patch.sig">
459: A source code patch exists which remedies this problem.</a>
460: <p>
461:
1.33 tj 462: <li id="p035_tty">
463: <strong>035: RELIABILITY FIX: July 22, 2020</strong>
464: <i>All architectures</i>
465: <br>
466: Only pty devices need reprint delays.
467: <br>
468: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/035_tty.patch.sig">
469: A source code patch exists which remedies this problem.</a>
470: <p>
471:
1.34 bluhm 472: <li id="p036_iked">
473: <strong>036: SECURITY FIX: July 27, 2020</strong>
474: <i>All architectures</i>
475: <br>
476: In iked, incorrect use of EVP_PKEY_cmp allows an authentication bypass.
477: <br>
478: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/036_iked.patch.sig">
479: A source code patch exists which remedies this problem.</a>
480: <p>
481:
1.35 tj 482: <li id="p037_ximcp">
483: <strong>037: SECURITY FIX: July 31, 2020</strong>
484: <i>All architectures</i>
485: <br>
486: Malformed messages can cause heap corruption in the X Input Method
487: client implementation in libX11.
488: <br>
489: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/037_ximcp.patch.sig">
490: A source code patch exists which remedies this problem.</a>
491: <p>
492:
493: <li id="p038_dix">
494: <strong>038: SECURITY FIX: July 31, 2020</strong>
495: <i>All architectures</i>
496: <br>
497: Pixmaps inside the xserver were an info leak.
498: <br>
499: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/038_dix.patch.sig">
500: A source code patch exists which remedies this problem.</a>
501: <p>
502:
1.36 tj 503: <li id="p039_ximcp">
504: <strong>039: RELIABILITY FIX: August 7, 2020</strong>
505: <i>All architectures</i>
506: <br>
507: The recent security errata 037 broke X11 input methods.
508: <br>
509: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/039_ximcp.patch.sig">
510: A source code patch exists which remedies this problem.</a>
511: <p>
512:
1.37 tj 513: <li id="p040_xinitom">
514: <strong>040: SECURITY FIX: August 25, 2020</strong>
515: <i>All architectures</i>
516: <br>
517: An integer overflow in libX11 could lead to a double free.
518: Additionally fix a regression in ximcp.
519: <br>
520: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/040_xinitom.patch.sig">
521: A source code patch exists which remedies this problem.</a>
522: <p>
523:
524: <li id="p041_xserverlen">
525: <strong>041: SECURITY FIX: August 25, 2020</strong>
526: <i>All architectures</i>
527: <br>
528: Various X server extensions had deficient input validation.
529: <br>
530: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/041_xserverlen.patch.sig">
531: A source code patch exists which remedies this problem.</a>
532: <p>
533:
1.38 tj 534: <li id="p042_amdgpu">
535: <strong>042: SECURITY FIX: September 5, 2020</strong>
536: <i>amd64, arm64</i>
537: <br>
538: A buffer overflow was discovered in an amdgpu ioctl.
539: <br>
540: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/042_amdgpu.patch.sig">
541: A source code patch exists which remedies this problem.</a>
542: <p>
543:
1.1 deraadt 544: </ul>
545:
1.17 tj 546: <hr>