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