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