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