Annotation of www/errata63.html, Revision 1.32
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2: <html>
3: <head>
4: <title>OpenBSD 6.3 Errata</title>
5: <meta name="description" content="the OpenBSD errata page">
6: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
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: </head>
11:
12: <!--
13: IMPORTANT REMINDER
14: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
15: -->
16: <body bgcolor="#ffffff" text="#000000" link="#23238E">
17:
18: <h2>
19: <a href="index.html">
20: <font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>
21: <font color="#e00000">6.3 Errata</font>
22: </h2>
23: <hr>
24:
25: For errata on a certain release, click below:<br>
26: <a href="errata21.html">2.1</a>,
27: <a href="errata22.html">2.2</a>,
28: <a href="errata23.html">2.3</a>,
29: <a href="errata24.html">2.4</a>,
30: <a href="errata25.html">2.5</a>,
31: <a href="errata26.html">2.6</a>,
32: <a href="errata27.html">2.7</a>,
33: <a href="errata28.html">2.8</a>,
34: <a href="errata29.html">2.9</a>,
35: <a href="errata30.html">3.0</a>,
36: <a href="errata31.html">3.1</a>,
37: <a href="errata32.html">3.2</a>,
38: <a href="errata33.html">3.3</a>,
39: <a href="errata34.html">3.4</a>,
40: <a href="errata35.html">3.5</a>,
41: <a href="errata36.html">3.6</a>,
42: <br>
43: <a href="errata37.html">3.7</a>,
44: <a href="errata38.html">3.8</a>,
45: <a href="errata39.html">3.9</a>,
46: <a href="errata40.html">4.0</a>,
47: <a href="errata41.html">4.1</a>,
48: <a href="errata42.html">4.2</a>,
49: <a href="errata43.html">4.3</a>,
50: <a href="errata44.html">4.4</a>,
51: <a href="errata45.html">4.5</a>,
52: <a href="errata46.html">4.6</a>,
53: <a href="errata47.html">4.7</a>,
54: <a href="errata48.html">4.8</a>,
55: <a href="errata49.html">4.9</a>,
56: <a href="errata50.html">5.0</a>,
57: <a href="errata51.html">5.1</a>,
58: <a href="errata52.html">5.2</a>,
59: <br>
60: <a href="errata53.html">5.3</a>,
61: <a href="errata54.html">5.4</a>,
62: <a href="errata55.html">5.5</a>,
63: <a href="errata56.html">5.6</a>,
64: <a href="errata57.html">5.7</a>,
65: <a href="errata58.html">5.8</a>,
66: <a href="errata59.html">5.9</a>,
67: <a href="errata60.html">6.0</a>,
68: <a href="errata61.html">6.1</a>,
1.19 deraadt 69: <a href="errata62.html">6.2</a>,
1.32 ! deraadt 70: <a href="errata64.html">6.4</a>,
! 71: <a href="errata65.html">6.5</a>.
1.1 deraadt 72: <hr>
73:
74: <p>
75: Patches for the OpenBSD base system are distributed as unified diffs.
76: Each patch is cryptographically signed with the
77: <a href="https://man.openbsd.org/OpenBSD-6.3/signify.1">signify(1)</a> tool and contains
78: usage instructions.
79: All the following patches are also available in one
80: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3.tar.gz">tar.gz file</a>
81: for convenience.
82:
83: <p>
84: Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
85: utility can be used to apply binary updates on the following architectures:
86: amd64, i386, arm64.
87:
88: <p>
89: Patches for supported releases are also incorporated into the
90: <a href="stable.html">-stable branch</a>, which is maintained for one year
91: after release.
92:
93: <hr>
94:
95: <ul>
96:
1.2 afresh1 97: <li id="p001_perl">
98: <font color="#009000">
99: <strong>001: SECURITY FIX: April 14, 2018</strong></font>
100: <i>All architectures</i>
101: <br>
102: Heap overflows exist in perl which can lead to segmentation faults,
103: crashes, and reading memory past the buffer.
104: <br>
105: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/001_perl.patch.sig">
106: A source code patch exists which remedies this problem.</a>
107: <p>
1.1 deraadt 108:
1.4 tj 109: <li id="p002_libtls">
1.3 tj 110: <font color="#009000">
111: <strong>002: RELIABILITY FIX: April 21, 2018</strong></font>
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.3 tj 122: <font color="#009000">
123: <strong>003: RELIABILITY FIX: April 21, 2018</strong></font>
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">
133: <font color="#009000">
134: <strong>004: SECURITY FIX: April 21, 2018</strong></font>
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">
145: <font color="#009000">
146: <strong>005: RELIABILITY FIX: April 21, 2018</strong></font>
147: <i>All architectures</i>
148: <br>
149: httpd can leak file descriptors when servicing range requests.
150: <br>
151: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/005_httpd.patch.sig">
152: A source code patch exists which remedies this problem.</a>
153: <p>
154:
1.5 tj 155: <li id="p006_ipseclen">
156: <font color="#009000">
157: <strong>006: RELIABILITY FIX: May 8, 2018</strong></font>
158: <i>All architectures</i>
159: <br>
160: Incorrect handling of fragmented IPsec packets could result in a system crash.
161: <br>
162: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/006_ipseclen.patch.sig">
163: A source code patch exists which remedies this problem.</a>
164: <p>
165:
166: <li id="p007_libcrypto">
167: <font color="#009000">
168: <strong>007: RELIABILITY FIX: May 8, 2018</strong></font>
169: <i>All architectures</i>
170: <br>
171: Incorrect checks in libcrypto can prevent Diffie-Hellman Exchange operations
172: from working.
173: <br>
174: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/007_libcrypto.patch.sig">
175: A source code patch exists which remedies this problem.</a>
176: <p>
177:
1.6 tj 178: <li id="p008_ipsecout">
179: <font color="#009000">
180: <strong>008: RELIABILITY FIX: May 17, 2018</strong></font>
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">
190: <font color="#009000">
191: <strong>009: SECURITY FIX: June 14, 2018</strong></font>
192: <i>All architectures</i>
193: <br>
194: DSA and ECDSA signature generation can potentially leak secret information
195: to a timing side-channel attack.
196: <br>
197: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/009_libcrypto.patch.sig">
198: A source code patch exists which remedies this problem.</a>
199: <p>
200:
1.8 tj 201: <li id="p010_intelfpu">
202: <font color="#009000">
203: <strong>010: SECURITY FIX: June 17, 2018</strong></font>
204: <i>amd64</i>
205: <br>
206: Intel CPUs speculatively access FPU registers even when the FPU is disabled,
207: so data (including AES keys) from previous contexts could be discovered
208: if using the lazy-save approach.
209: <br>
210: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/010_intelfpu.patch.sig">
211: A source code patch exists which remedies this problem.</a>
212: <p>
213:
1.9 afresh1 214: <li id="p011_perl">
215: <font color="#009000">
216: <strong>011: SECURITY FIX: June 21, 2018</strong></font>
217: <i>All architectures</i>
218: <br>
219: Perl's Archive::Tar module could be made to write files outside of
220: its working directory.
221: <br>
222: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/011_perl.patch.sig">
223: A source code patch exists which remedies this problem.</a>
224: <p>
225:
1.10 tj 226: <li id="p012_execsize">
227: <font color="#009000">
228: <strong>012: RELIABILITY FIX: July 25, 2018</strong></font>
229: <i>All architectures</i>
230: <br>
231: A regular user could trigger a kernel panic by executing an invalid
232: ELF binary.
233: <br>
234: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/012_execsize.patch.sig">
235: A source code patch exists which remedies this problem.</a>
236: <p>
237:
238: <li id="p013_ipsecexpire">
239: <font color="#009000">
240: <strong>013: RELIABILITY FIX: July 25, 2018</strong></font>
241: <i>All architectures</i>
242: <br>
243: When an IPsec key expired, the kernel could panic due to unfinished
244: timeout tasks.
245: <br>
246: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/013_ipsecexpire.patch.sig">
247: A source code patch exists which remedies this problem.</a>
248: <p>
249:
1.11 tj 250: <li id="p014_amdlfence">
251: <font color="#009000">
252: <strong>014: SECURITY FIX: July 31, 2018</strong></font>
253: <i>amd64 and i386</i>
254: <br>
255: On AMD CPUs, set a chicken bit which turns LFENCE into a serialization
256: instruction against speculation.
257: <br>
258: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/014_amdlfence.patch.sig">
259: A source code patch exists which remedies this problem.</a>
260: <p>
261:
262: <li id="p015_ioport">
263: <font color="#009000">
1.13 tj 264: <strong>015: SECURITY FIX: July 31, 2018</strong></font>
1.11 tj 265: <i>i386</i>
266: <br>
267: IO port permissions were incorrectly restricted.
268: <br>
269: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/015_ioport.patch.sig">
270: A source code patch exists which remedies this problem.</a>
271: <p>
272:
1.14 tj 273: <li id="p016_fpuinit">
274: <font color="#009000">
1.16 deraadt 275: <strong>016: RELIABILITY FIX: August 4, 2018</strong></font>
1.14 tj 276: <i>amd64</i>
277: <br>
278: Incorrect initialization of the FPU caused floating point exceptions
279: when running on Xen.
280: <br>
281: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/016_fpuinit.patch.sig">
282: A source code patch exists which remedies this problem.</a>
283: <p>
284:
1.17 tj 285: <li id="p017_fpufork">
286: <font color="#009000">
287: <strong>017: SECURITY FIX: August 24, 2018</strong></font>
288: <i>amd64</i>
289: <br>
290: State from the FPU of one userland process could be exposed to other processes.
291: <br>
292: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/017_fpufork.patch.sig">
293: A source code patch exists which remedies this problem.</a>
294: <p>
295:
296: <li id="p018_vmml1tf">
297: <font color="#009000">
298: <strong>018: SECURITY FIX: August 24, 2018</strong></font>
299: <i>amd64</i>
300: <br>
301: The Intel L1TF bug allows a vmm guest to read host memory.
302: Install the CPU firmware using fw_update(1) and apply this workaround.
303: <br>
304: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/018_vmml1tf.patch.sig">
305: A source code patch exists which remedies this problem.</a>
306: <p>
307:
1.18 tj 308: <li id="p019_ldtr">
309: <font color="#009000">
310: <strong>019: SECURITY FIX: September 21, 2018</strong></font>
311: <i>amd64</i>
312: <br>
313: On AMD CPUs, LDTR must be managed crossing between VMs.
314: <br>
315: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/019_ldtr.patch.sig">
316: A source code patch exists which remedies this problem.</a>
317: <p>
318:
1.20 tj 319: <li id="p020_xserver">
320: <font color="#009000">
321: <strong>020: SECURITY FIX: October 25, 2018</strong></font>
322: <i>All architectures</i>
323: <br>
324: The Xorg X server incorrectly validates certain options, allowing arbitrary
325: files to be overwritten.
326: As an immediate (temporary) workaround, the Xorg binary can be disabled
327: by running: <code>chmod u-s /usr/X11R6/bin/Xorg</code>
328: <br>
329: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/020_xserver.patch.sig">
330: A source code patch exists which remedies this problem.</a>
331: <p>
332:
1.21 tj 333: <li id="p021_syspatch">
334: <font color="#009000">
335: <strong>021: RELIABILITY FIX: November 2, 2018</strong></font>
336: <i>i386, amd64, arm64</i>
337: <br>
338: The syspatch utility incorrectly handles symbolic links.
339: <br>
340: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/021_syspatch.patch.sig">
341: A source code patch exists which remedies this problem.</a>
342: <p>
343:
1.22 tj 344: <li id="p022_blinding">
345: <font color="#009000">
346: <strong>022: SECURITY FIX: November 17, 2018</strong></font>
347: <i>All architectures</i>
348: <br>
349: Timing side channels may leak information about DSA and ECDSA private keys.
350: <br>
351: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/022_blinding.patch.sig">
352: A source code patch exists which remedies this problem.</a>
353: <p>
354:
355: <li id="p023_lockf">
356: <font color="#009000">
357: <strong>023: RELIABILITY FIX: November 17, 2018</strong></font>
358: <i>All architectures</i>
359: <br>
360: A recent change to POSIX file locks could cause incorrect results
361: during lock acquisition.
362: <br>
363: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/023_lockf.patch.sig">
364: A source code patch exists which remedies this problem.</a>
365: <p>
366:
1.23 tj 367: <li id="p024_perl">
368: <font color="#009000">
369: <strong>024: SECURITY FIX: November 29, 2018</strong></font>
370: <i>All architectures</i>
371: <br>
372: Various overflows exist in perl.
373: <br>
374: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/024_perl.patch.sig">
375: A source code patch exists which remedies this problem.</a>
376: <p>
377:
378: <li id="p025_uipc">
379: <font color="#009000">
380: <strong>025: RELIABILITY FIX: November 29, 2018</strong></font>
381: <i>All architectures</i>
382: <br>
383: UNIX domain sockets leak kernel memory with MSG_PEEK on SCM_RIGHTS, or can
384: attempt excessive memory allocations leading to a crash.
385: <br>
386: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/025_uipc.patch.sig">
387: A source code patch exists which remedies this problem.</a>
388: <p>
389:
1.24 tj 390: <li id="p026_recvwait">
391: <font color="#009000">
392: <strong>026: RELIABILITY FIX: December 20, 2018</strong></font>
393: <i>All architectures</i>
394: <br>
395: While recv(2) with the MSG_WAITALL flag was receiving control
396: messages from a socket, the kernel could panic.
397: <br>
398: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/026_recvwait.patch.sig">
399: A source code patch exists which remedies this problem.</a>
400: <p>
401:
1.25 tj 402: <li id="p027_pcbopts">
403: <font color="#009000">
404: <strong>027: SECURITY FIX: December 22, 2018</strong></font>
405: <i>All architectures</i>
406: <br>
407: The setsockopt(2) system call could overflow mbuf cluster kernel
408: memory by 4 bytes.
409: <br>
410: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/027_pcbopts.patch.sig">
411: A source code patch exists which remedies this problem.</a>
412: <p>
413:
1.28 tj 414: <li id="p028_mincore">
415: <font color="#009000">
416: <strong>028: SECURITY FIX: February 5, 2019</strong></font>
417: <i>All architectures</i>
418: <br>
419: The mincore() system call can be used to observe memory access patterns
420: of other processes.
421: <br>
422: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/028_mincore.patch.sig">
423: A source code patch exists which remedies this problem.</a>
424: <p>
425:
426: <li id="p029_nfs">
427: <font color="#009000">
428: <strong>029: RELIABILITY FIX: February 5, 2019</strong></font>
429: <i>All architectures</i>
430: <br>
431: Missing length checks in the NFS server and client can lead to crashes
432: and other errors.
433: <br>
434: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/029_nfs.patch.sig">
435: A source code patch exists which remedies this problem.</a>
436: <p>
437:
1.29 tj 438: <li id="p030_pf6frag">
439: <font color="#009000">
440: <strong>030: SECURITY FIX: March 1, 2019</strong></font>
441: <i>All architectures</i>
442: <br>
443: Fragmented IPv6 packets may be erroneously passed by pf or lead to a crash.
444: <br>
445: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/030_pf6frag.patch.sig">
446: A source code patch exists which remedies this problem.</a>
447: <p>
448:
1.30 tj 449: <li id="p031_pficmp">
450: <font color="#009000">
451: <strong>031: SECURITY FIX: March 22, 2019</strong></font>
452: <i>All architectures</i>
453: <br>
454: A state in pf could pass ICMP packets to a destination IP address
455: that did not match the state.
456: <br>
457: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/031_pficmp.patch.sig">
458: A source code patch exists which remedies this problem.</a>
459: <p>
460:
1.31 tj 461: <li id="p032_vmmints">
462: <font color="#009000">
463: <strong>032: SECURITY FIX: March 27, 2019</strong></font>
464: <i>amd64 and i386</i>
465: <br>
466: GDT and IDT limits were improperly restored during VMM context switches.
467: <br>
468: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/032_vmmints.patch.sig">
469: A source code patch exists which remedies this problem.</a>
470: <p>
471:
1.1 deraadt 472: </ul>
473:
474: <hr>
475:
476: </body>
477: </html>
![[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