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