Annotation of www/errata63.html, Revision 1.46
1.35 bentley 1: <!doctype html>
2: <html lang=en id=errata>
3: <meta charset=utf-8>
4:
1.1 deraadt 5: <title>OpenBSD 6.3 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/errata63.html">
10:
11: <!--
12: IMPORTANT REMINDER
13: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
14: -->
15:
1.35 bentley 16: <h2 id=OpenBSD>
1.1 deraadt 17: <a href="index.html">
1.35 bentley 18: <i>Open</i><b>BSD</b></a>
19: 6.3 Errata
1.1 deraadt 20: </h2>
21: <hr>
22:
23: For errata on a certain release, click below:<br>
1.38 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.38 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.38 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>,
1.19 deraadt 68: <a href="errata62.html">6.2</a>,
1.32 deraadt 69: <a href="errata64.html">6.4</a>,
1.37 deraadt 70: <a href="errata65.html">6.5</a>,
1.39 deraadt 71: <a href="errata66.html">6.6</a>,
1.40 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>,
! 79: <a href="errata73.html">7.3</a>.
1.1 deraadt 80: <hr>
81:
82: <p>
83: Patches for the OpenBSD base system are distributed as unified diffs.
84: Each patch is cryptographically signed with the
85: <a href="https://man.openbsd.org/OpenBSD-6.3/signify.1">signify(1)</a> tool and contains
86: usage instructions.
87: All the following patches are also available in one
88: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3.tar.gz">tar.gz file</a>
89: for convenience.
90:
91: <p>
92: Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
93: utility can be used to apply binary updates on the following architectures:
94: amd64, i386, arm64.
95:
96: <p>
97: Patches for supported releases are also incorporated into the
1.33 tj 98: <a href="stable.html">-stable branch</a>.
1.1 deraadt 99:
100: <hr>
101:
102: <ul>
103:
1.2 afresh1 104: <li id="p001_perl">
1.35 bentley 105: <strong>001: SECURITY FIX: April 14, 2018</strong>
1.2 afresh1 106: <i>All architectures</i>
107: <br>
108: Heap overflows exist in perl which can lead to segmentation faults,
109: crashes, and reading memory past the buffer.
110: <br>
111: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/001_perl.patch.sig">
112: A source code patch exists which remedies this problem.</a>
113: <p>
1.1 deraadt 114:
1.4 tj 115: <li id="p002_libtls">
1.35 bentley 116: <strong>002: RELIABILITY FIX: April 21, 2018</strong>
1.3 tj 117: <i>All architectures</i>
118: <br>
1.4 tj 119: Additional data is inadvertently removed when private keys are cleared from
120: TLS configuration, which can prevent OCSP from functioning correctly.
1.3 tj 121: <br>
1.4 tj 122: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/002_libtls.patch.sig">
1.3 tj 123: A source code patch exists which remedies this problem.</a>
124: <p>
125:
1.4 tj 126: <li id="p003_arp">
1.35 bentley 127: <strong>003: RELIABILITY FIX: April 21, 2018</strong>
1.3 tj 128: <i>All architectures</i>
129: <br>
1.4 tj 130: ARP replies could be sent on the wrong member of a bridge(4) interface.
1.3 tj 131: <br>
1.4 tj 132: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/003_arp.patch.sig">
1.3 tj 133: A source code patch exists which remedies this problem.</a>
134: <p>
135:
136: <li id="p004_gif">
1.35 bentley 137: <strong>004: SECURITY FIX: April 21, 2018</strong>
1.3 tj 138: <i>All architectures</i>
139: <br>
140: In the gif(4) interface, use the specified protocol for IPv6, plug
141: a mbuf leak and avoid a use after free.
142: <br>
143: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/004_gif.patch.sig">
144: A source code patch exists which remedies this problem.</a>
145: <p>
146:
147: <li id="p005_httpd">
1.35 bentley 148: <strong>005: RELIABILITY FIX: April 21, 2018</strong>
1.3 tj 149: <i>All architectures</i>
150: <br>
151: httpd can leak file descriptors when servicing range requests.
152: <br>
153: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/005_httpd.patch.sig">
154: A source code patch exists which remedies this problem.</a>
155: <p>
156:
1.5 tj 157: <li id="p006_ipseclen">
1.35 bentley 158: <strong>006: RELIABILITY FIX: May 8, 2018</strong>
1.5 tj 159: <i>All architectures</i>
160: <br>
161: Incorrect handling of fragmented IPsec packets could result in a system crash.
162: <br>
163: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/006_ipseclen.patch.sig">
164: A source code patch exists which remedies this problem.</a>
165: <p>
166:
167: <li id="p007_libcrypto">
1.35 bentley 168: <strong>007: RELIABILITY FIX: May 8, 2018</strong>
1.5 tj 169: <i>All architectures</i>
170: <br>
171: Incorrect checks in libcrypto can prevent Diffie-Hellman Exchange operations
172: from working.
173: <br>
174: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/007_libcrypto.patch.sig">
175: A source code patch exists which remedies this problem.</a>
176: <p>
177:
1.6 tj 178: <li id="p008_ipsecout">
1.35 bentley 179: <strong>008: RELIABILITY FIX: May 17, 2018</strong>
1.6 tj 180: <i>All architectures</i>
181: <br>
182: A malicious packet can cause a kernel crash when using IPsec over IPv6.
183: <br>
184: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/008_ipsecout.patch.sig">
185: A source code patch exists which remedies this problem.</a>
186: <p>
187:
1.7 tb 188: <li id="p009_libcrypto">
1.35 bentley 189: <strong>009: SECURITY FIX: June 14, 2018</strong>
1.7 tb 190: <i>All architectures</i>
191: <br>
192: DSA and ECDSA signature generation can potentially leak secret information
193: to a timing side-channel attack.
194: <br>
195: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/009_libcrypto.patch.sig">
196: A source code patch exists which remedies this problem.</a>
197: <p>
198:
1.8 tj 199: <li id="p010_intelfpu">
1.35 bentley 200: <strong>010: SECURITY FIX: June 17, 2018</strong>
1.8 tj 201: <i>amd64</i>
202: <br>
203: Intel CPUs speculatively access FPU registers even when the FPU is disabled,
204: so data (including AES keys) from previous contexts could be discovered
205: if using the lazy-save approach.
206: <br>
207: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/010_intelfpu.patch.sig">
208: A source code patch exists which remedies this problem.</a>
209: <p>
210:
1.9 afresh1 211: <li id="p011_perl">
1.35 bentley 212: <strong>011: SECURITY FIX: June 21, 2018</strong>
1.9 afresh1 213: <i>All architectures</i>
214: <br>
215: Perl's Archive::Tar module could be made to write files outside of
216: its working directory.
217: <br>
218: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/011_perl.patch.sig">
219: A source code patch exists which remedies this problem.</a>
220: <p>
221:
1.10 tj 222: <li id="p012_execsize">
1.35 bentley 223: <strong>012: RELIABILITY FIX: July 25, 2018</strong>
1.10 tj 224: <i>All architectures</i>
225: <br>
226: A regular user could trigger a kernel panic by executing an invalid
227: ELF binary.
228: <br>
229: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/012_execsize.patch.sig">
230: A source code patch exists which remedies this problem.</a>
231: <p>
232:
233: <li id="p013_ipsecexpire">
1.35 bentley 234: <strong>013: RELIABILITY FIX: July 25, 2018</strong>
1.10 tj 235: <i>All architectures</i>
236: <br>
237: When an IPsec key expired, the kernel could panic due to unfinished
238: timeout tasks.
239: <br>
240: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/013_ipsecexpire.patch.sig">
241: A source code patch exists which remedies this problem.</a>
242: <p>
243:
1.11 tj 244: <li id="p014_amdlfence">
1.35 bentley 245: <strong>014: SECURITY FIX: July 31, 2018</strong>
1.11 tj 246: <i>amd64 and i386</i>
247: <br>
248: On AMD CPUs, set a chicken bit which turns LFENCE into a serialization
249: instruction against speculation.
250: <br>
251: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/014_amdlfence.patch.sig">
252: A source code patch exists which remedies this problem.</a>
253: <p>
254:
255: <li id="p015_ioport">
1.35 bentley 256: <strong>015: SECURITY FIX: July 31, 2018</strong>
1.11 tj 257: <i>i386</i>
258: <br>
259: IO port permissions were incorrectly restricted.
260: <br>
261: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/015_ioport.patch.sig">
262: A source code patch exists which remedies this problem.</a>
263: <p>
264:
1.14 tj 265: <li id="p016_fpuinit">
1.35 bentley 266: <strong>016: RELIABILITY FIX: August 4, 2018</strong>
1.14 tj 267: <i>amd64</i>
268: <br>
269: Incorrect initialization of the FPU caused floating point exceptions
270: when running on Xen.
271: <br>
272: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/016_fpuinit.patch.sig">
273: A source code patch exists which remedies this problem.</a>
274: <p>
275:
1.17 tj 276: <li id="p017_fpufork">
1.35 bentley 277: <strong>017: SECURITY FIX: August 24, 2018</strong>
1.17 tj 278: <i>amd64</i>
279: <br>
280: State from the FPU of one userland process could be exposed to other processes.
281: <br>
282: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/017_fpufork.patch.sig">
283: A source code patch exists which remedies this problem.</a>
284: <p>
285:
286: <li id="p018_vmml1tf">
1.35 bentley 287: <strong>018: SECURITY FIX: August 24, 2018</strong>
1.17 tj 288: <i>amd64</i>
289: <br>
290: The Intel L1TF bug allows a vmm guest to read host memory.
291: Install the CPU firmware using fw_update(1) and apply this workaround.
292: <br>
293: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/018_vmml1tf.patch.sig">
294: A source code patch exists which remedies this problem.</a>
295: <p>
296:
1.18 tj 297: <li id="p019_ldtr">
1.35 bentley 298: <strong>019: SECURITY FIX: September 21, 2018</strong>
1.18 tj 299: <i>amd64</i>
300: <br>
301: On AMD CPUs, LDTR must be managed crossing between VMs.
302: <br>
303: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/019_ldtr.patch.sig">
304: A source code patch exists which remedies this problem.</a>
305: <p>
306:
1.20 tj 307: <li id="p020_xserver">
1.35 bentley 308: <strong>020: SECURITY FIX: October 25, 2018</strong>
1.20 tj 309: <i>All architectures</i>
310: <br>
1.36 deraadt 311: The Xorg X server incorrectly validates certain options, allowing arbitrary
1.20 tj 312: files to be overwritten.
313: As an immediate (temporary) workaround, the Xorg binary can be disabled
314: by running: <code>chmod u-s /usr/X11R6/bin/Xorg</code>
315: <br>
316: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/020_xserver.patch.sig">
317: A source code patch exists which remedies this problem.</a>
318: <p>
319:
1.21 tj 320: <li id="p021_syspatch">
1.35 bentley 321: <strong>021: RELIABILITY FIX: November 2, 2018</strong>
1.21 tj 322: <i>i386, amd64, arm64</i>
323: <br>
324: The syspatch utility incorrectly handles symbolic links.
325: <br>
326: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/021_syspatch.patch.sig">
327: A source code patch exists which remedies this problem.</a>
328: <p>
329:
1.22 tj 330: <li id="p022_blinding">
1.35 bentley 331: <strong>022: SECURITY FIX: November 17, 2018</strong>
1.22 tj 332: <i>All architectures</i>
333: <br>
334: Timing side channels may leak information about DSA and ECDSA private keys.
335: <br>
336: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/022_blinding.patch.sig">
337: A source code patch exists which remedies this problem.</a>
338: <p>
339:
340: <li id="p023_lockf">
1.35 bentley 341: <strong>023: RELIABILITY FIX: November 17, 2018</strong>
1.22 tj 342: <i>All architectures</i>
343: <br>
344: A recent change to POSIX file locks could cause incorrect results
345: during lock acquisition.
346: <br>
347: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/023_lockf.patch.sig">
348: A source code patch exists which remedies this problem.</a>
349: <p>
350:
1.23 tj 351: <li id="p024_perl">
1.35 bentley 352: <strong>024: SECURITY FIX: November 29, 2018</strong>
1.23 tj 353: <i>All architectures</i>
354: <br>
355: Various overflows exist in perl.
356: <br>
357: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/024_perl.patch.sig">
358: A source code patch exists which remedies this problem.</a>
359: <p>
360:
361: <li id="p025_uipc">
1.35 bentley 362: <strong>025: RELIABILITY FIX: November 29, 2018</strong>
1.23 tj 363: <i>All architectures</i>
364: <br>
365: UNIX domain sockets leak kernel memory with MSG_PEEK on SCM_RIGHTS, or can
366: attempt excessive memory allocations leading to a crash.
367: <br>
368: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/025_uipc.patch.sig">
369: A source code patch exists which remedies this problem.</a>
370: <p>
371:
1.24 tj 372: <li id="p026_recvwait">
1.35 bentley 373: <strong>026: RELIABILITY FIX: December 20, 2018</strong>
1.24 tj 374: <i>All architectures</i>
375: <br>
376: While recv(2) with the MSG_WAITALL flag was receiving control
377: messages from a socket, the kernel could panic.
378: <br>
379: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/026_recvwait.patch.sig">
380: A source code patch exists which remedies this problem.</a>
381: <p>
382:
1.25 tj 383: <li id="p027_pcbopts">
1.35 bentley 384: <strong>027: SECURITY FIX: December 22, 2018</strong>
1.25 tj 385: <i>All architectures</i>
386: <br>
387: The setsockopt(2) system call could overflow mbuf cluster kernel
388: memory by 4 bytes.
389: <br>
390: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/027_pcbopts.patch.sig">
391: A source code patch exists which remedies this problem.</a>
392: <p>
393:
1.28 tj 394: <li id="p028_mincore">
1.35 bentley 395: <strong>028: SECURITY FIX: February 5, 2019</strong>
1.28 tj 396: <i>All architectures</i>
397: <br>
398: The mincore() system call can be used to observe memory access patterns
399: of other processes.
400: <br>
401: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/028_mincore.patch.sig">
402: A source code patch exists which remedies this problem.</a>
403: <p>
404:
405: <li id="p029_nfs">
1.35 bentley 406: <strong>029: RELIABILITY FIX: February 5, 2019</strong>
1.28 tj 407: <i>All architectures</i>
408: <br>
409: Missing length checks in the NFS server and client can lead to crashes
410: and other errors.
411: <br>
412: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/029_nfs.patch.sig">
413: A source code patch exists which remedies this problem.</a>
414: <p>
415:
1.29 tj 416: <li id="p030_pf6frag">
1.35 bentley 417: <strong>030: SECURITY FIX: March 1, 2019</strong>
1.29 tj 418: <i>All architectures</i>
419: <br>
420: Fragmented IPv6 packets may be erroneously passed by pf or lead to a crash.
421: <br>
422: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/030_pf6frag.patch.sig">
423: A source code patch exists which remedies this problem.</a>
424: <p>
425:
1.30 tj 426: <li id="p031_pficmp">
1.35 bentley 427: <strong>031: SECURITY FIX: March 22, 2019</strong>
1.30 tj 428: <i>All architectures</i>
429: <br>
430: A state in pf could pass ICMP packets to a destination IP address
431: that did not match the state.
432: <br>
433: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/031_pficmp.patch.sig">
434: A source code patch exists which remedies this problem.</a>
435: <p>
436:
1.31 tj 437: <li id="p032_vmmints">
1.35 bentley 438: <strong>032: SECURITY FIX: March 27, 2019</strong>
1.31 tj 439: <i>amd64 and i386</i>
440: <br>
441: GDT and IDT limits were improperly restored during VMM context switches.
442: <br>
443: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/032_vmmints.patch.sig">
444: A source code patch exists which remedies this problem.</a>
445: <p>
446:
1.34 tj 447: <li id="p033_rip6cksum">
1.35 bentley 448: <strong>033: RELIABILITY FIX: May 3, 2019</strong>
1.34 tj 449: <i>All architectures</i>
450: <br>
451: If a userland program sets the IPv6 checksum offset on a raw socket,
452: an incoming packet could crash the kernel. ospf6d is such a program.
453: <br>
454: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/033_rip6cksum.patch.sig">
455: A source code patch exists which remedies this problem.</a>
456: <p>
457:
1.1 deraadt 458: </ul>
459:
460: <hr>