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