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