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