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