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