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