Annotation of www/errata64.html, Revision 1.37
1.19 bentley 1: <!doctype html>
2: <html lang=en id=errata>
3: <meta charset=utf-8>
4:
1.1 deraadt 5: <title>OpenBSD 6.4 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">
1.7 deraadt 9: <link rel="canonical" href="https://www.openbsd.org/errata64.html">
1.1 deraadt 10:
11: <!--
12: IMPORTANT REMINDER
13: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
14: -->
15:
1.19 bentley 16: <h2 id=OpenBSD>
1.1 deraadt 17: <a href="index.html">
1.19 bentley 18: <i>Open</i><b>BSD</b></a>
19: 6.4 Errata
1.1 deraadt 20: </h2>
21: <hr>
22:
23: For errata on a certain release, click below:<br>
1.30 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.30 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.30 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>,
68: <a href="errata62.html">6.2</a>,
1.15 deraadt 69: <a href="errata63.html">6.3</a>,
1.27 deraadt 70: <a href="errata65.html">6.5</a>,
1.31 deraadt 71: <a href="errata66.html">6.6</a>,
1.32 deraadt 72: <a href="errata67.html">6.7</a>,
1.33 deraadt 73: <a href="errata68.html">6.8</a>,
1.34 tj 74: <br>
1.35 deraadt 75: <a href="errata69.html">6.9</a>,
1.36 deraadt 76: <a href="errata70.html">7.0</a>,
1.37 ! 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
1.3 tb 84: <a href="https://man.openbsd.org/OpenBSD-6.4/signify.1">signify(1)</a> tool and contains
1.1 deraadt 85: usage instructions.
86: All the following patches are also available in one
87: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4.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.29 tj 97: <a href="stable.html">-stable branch</a>.
1.1 deraadt 98:
99: <hr>
100:
101: <ul>
102:
1.4 tj 103: <li id="p001_xserver">
1.19 bentley 104: <strong>001: SECURITY FIX: October 25, 2018</strong>
1.4 tj 105: <i>All architectures</i>
106: <br>
107: The Xorg X server incorrectly validates certain options, allowing arbitrary
108: files to be overwritten.
109: As an immediate (temporary) workaround, the Xorg binary can be disabled
110: by running: <code>chmod u-s /usr/X11R6/bin/Xorg</code>
111: <br>
112: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/001_xserver.patch.sig">
113: A source code patch exists which remedies this problem.</a>
114: <p>
1.1 deraadt 115:
1.5 tj 116: <li id="p002_syspatch">
1.19 bentley 117: <strong>002: RELIABILITY FIX: November 2, 2018</strong>
1.5 tj 118: <i>i386, amd64, arm64</i>
119: <br>
120: The syspatch utility incorrectly handles symbolic links.
121: <br>
122: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/002_syspatch.patch.sig">
123: A source code patch exists which remedies this problem.</a>
124: <p>
125:
1.6 tj 126: <li id="p003_portsmash">
1.19 bentley 127: <strong>003: SECURITY FIX: November 17, 2018</strong>
1.6 tj 128: <i>All architectures</i>
129: <br>
130: The portsmash vulnerability allows exfiltration of elliptic curve keys.
131: <br>
132: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/003_portsmash.patch.sig">
133: A source code patch exists which remedies this problem.</a>
134: <p>
135:
136: <li id="p004_lockf">
1.19 bentley 137: <strong>004: RELIABILITY FIX: November 17, 2018</strong>
1.6 tj 138: <i>All architectures</i>
139: <br>
140: A recent change to POSIX file locks could cause incorrect results
141: during lock acquisition.
142: <br>
143: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/004_lockf.patch.sig">
144: A source code patch exists which remedies this problem.</a>
145: <p>
146:
1.8 tj 147: <li id="p005_perl">
1.19 bentley 148: <strong>005: SECURITY FIX: November 29, 2018</strong>
1.8 tj 149: <i>All architectures</i>
150: <br>
151: Various overflows exist in perl.
152: <br>
153: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/005_perl.patch.sig">
154: A source code patch exists which remedies this problem.</a>
155: <p>
156:
157: <li id="p006_uipc">
1.19 bentley 158: <strong>006: RELIABILITY FIX: November 29, 2018</strong>
1.8 tj 159: <i>All architectures</i>
160: <br>
161: UNIX domain sockets leak kernel memory with MSG_PEEK on SCM_RIGHTS, or can
162: attempt excessive memory allocations leading to a crash.
163: <br>
164: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/006_uipc.patch.sig">
165: A source code patch exists which remedies this problem.</a>
166: <p>
167:
168: <li id="p007_smtpd">
1.19 bentley 169: <strong>007: RELIABILITY FIX: November 29, 2018</strong>
1.8 tj 170: <i>All architectures</i>
171: <br>
172: The mail.mda and mail.lmtp delivery agents were not reporting temporary
173: failures correctly, causing smtpd to bounce messages in some cases where
174: it should have retried them.
175: <br>
176: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/007_smtpd.patch.sig">
177: A source code patch exists which remedies this problem.</a>
178: <p>
179:
180: <li id="p008_qcow2">
1.19 bentley 181: <strong>008: RELIABILITY FIX: November 29, 2018</strong>
1.8 tj 182: <i>amd64 and i386</i>
183: <br>
184: Writing more than 4GB to a qcow2 volume corrupts the virtual disk.
185: <br>
186: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/008_qcow2.patch.sig">
187: A source code patch exists which remedies this problem.</a>
188: <p>
189:
1.9 tj 190: <li id="p009_recvwait">
1.19 bentley 191: <strong>009: RELIABILITY FIX: December 20, 2018</strong>
1.9 tj 192: <i>All architectures</i>
193: <br>
194: While recv(2) with the MSG_WAITALL flag was receiving control
195: messages from a socket, the kernel could panic.
196: <br>
197: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/009_recvwait.patch.sig">
198: A source code patch exists which remedies this problem.</a>
199: <p>
200:
1.10 tj 201: <li id="p010_pcbopts">
1.19 bentley 202: <strong>010: SECURITY FIX: December 22, 2018</strong>
1.10 tj 203: <i>All architectures</i>
204: <br>
205: The setsockopt(2) system call could overflow mbuf cluster kernel
206: memory by 4 bytes.
207: <br>
208: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/010_pcbopts.patch.sig">
209: A source code patch exists which remedies this problem.</a>
210: <p>
211:
1.11 tj 212: <li id="p011_mincore">
1.19 bentley 213: <strong>011: SECURITY FIX: January 27, 2019</strong>
1.11 tj 214: <i>All architectures</i>
215: <br>
216: The mincore() system call can be used to observe memory access patterns
217: of other processes.
218: <br>
219: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/011_mincore.patch.sig">
220: A source code patch exists which remedies this problem.</a>
221: <p>
222:
223: <li id="p012_nfs">
1.19 bentley 224: <strong>012: RELIABILITY FIX: January 27, 2019</strong>
1.11 tj 225: <i>All architectures</i>
226: <br>
227: Missing length checks in the NFS server and client can lead to crashes
228: and other errors.
229: <br>
230: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/012_nfs.patch.sig">
231: A source code patch exists which remedies this problem.</a>
232: <p>
233:
234: <li id="p013_unveil">
1.19 bentley 235: <strong>013: SECURITY FIX: January 27, 2019</strong>
1.11 tj 236: <i>All architectures</i>
237: <br>
238: The unveil() system call can leak memory.
239: <br>
240: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/013_unveil.patch.sig">
241: A source code patch exists which remedies this problem.</a>
242: <p>
243:
1.12 tj 244: <li id="p014_pf6frag">
1.19 bentley 245: <strong>014: SECURITY FIX: March 1, 2019</strong>
1.12 tj 246: <i>All architectures</i>
247: <br>
248: Fragmented IPv6 packets may be erroneously passed by pf or lead to a crash.
249: <br>
250: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/014_pf6frag.patch.sig">
251: A source code patch exists which remedies this problem.</a>
252: <p>
253:
1.13 tj 254: <li id="p015_pficmp">
1.19 bentley 255: <strong>015: SECURITY FIX: March 22, 2019</strong>
1.13 tj 256: <i>All architectures</i>
257: <br>
258: A state in pf could pass ICMP packets to a destination IP address
259: that did not match the state.
260: <br>
261: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/015_pficmp.patch.sig">
262: A source code patch exists which remedies this problem.</a>
263: <p>
264:
1.14 tj 265: <li id="p016_vmmints">
1.19 bentley 266: <strong>016: SECURITY FIX: March 27, 2019</strong>
1.14 tj 267: <i>amd64 and i386</i>
268: <br>
269: GDT and IDT limits were improperly restored during VMM context switches.
270: <br>
271: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/016_vmmints.patch.sig">
272: A source code patch exists which remedies this problem.</a>
273: <p>
274:
1.16 tj 275: <li id="p017_rip6cksum">
1.19 bentley 276: <strong>017: RELIABILITY FIX: May 3, 2019</strong>
1.16 tj 277: <i>All architectures</i>
278: <br>
279: If a userland program sets the IPv6 checksum offset on a raw socket,
280: an incoming packet could crash the kernel. ospf6d is such a program.
281: <br>
282: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/017_rip6cksum.patch.sig">
283: A source code patch exists which remedies this problem.</a>
284: <p>
285:
1.20 tj 286: <li id="p018_mds">
287: <strong>018: SECURITY FIX: May 29, 2019</strong>
288: <i>amd64</i>
289: <br>
290: Intel CPUs have a cross privilege side-channel attack (MDS).
291: <br>
292: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/018_mds.patch.sig">
293: A source code patch exists which remedies this problem.</a>
294: <p>
295:
1.21 tj 296: <li id="p019_tcpsack">
297: <strong>019: RELIABILITY FIX: July 25, 2019</strong>
1.22 tj 298: <i>All architectures</i>
1.21 tj 299: <br>
300: By creating long chains of TCP SACK holes, an attacker could possibly
301: slow down the system temporarily.
302: <br>
303: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/019_tcpsack.patch.sig">
304: A source code patch exists which remedies this problem.</a>
305: <p>
306:
1.23 tj 307: <li id="p020_smtpd">
308: <strong>020: RELIABILITY FIX: August 2, 2019</strong>
309: <i>All architectures</i>
310: <br>
311: smtpd can crash on excessively large input, causing a denial of service.
312: <br>
313: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/020_smtpd.patch.sig">
314: A source code patch exists which remedies this problem.</a>
315: <p>
316:
1.24 tj 317: <li id="p021_swapgs">
318: <strong>021: SECURITY FIX: August 9, 2019</strong>
319: <i>amd64</i>
320: <br>
321: Intel CPUs have another cross privilege side-channel attack. (SWAPGS)
322: <br>
323: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/021_swapgs.patch.sig">
324: A source code patch exists which remedies this problem.</a>
325: <p>
326:
1.25 tj 327: <li id="p022_resume">
328: <strong>022: RELIABILITY FIX: September 2, 2019</strong>
329: <i>amd64</i>
330: <br>
331: Resume forgot to restore MSR/PAT configuration.
332: <br>
333: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/022_resume.patch.sig">
334: A source code patch exists which remedies this problem.</a>
335: <p>
336:
337: <li id="p023_frag6ecn">
338: <strong>023: RELIABILITY FIX: September 2, 2019</strong>
339: <i>All architectures</i>
340: <br>
341: When processing ECN bits on incoming IPv6 fragments, the kernel
342: could crash. Per default pf fragment reassemble prevents the crash.
343: <br>
344: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/023_frag6ecn.patch.sig">
345: A source code patch exists which remedies this problem.</a>
346: <p>
347:
1.26 tj 348: <li id="p024_expat">
349: <strong>024: SECURITY FIX: September 14, 2019</strong>
350: <i>All architectures</i>
351: <br>
352: Libexpat 2.2.6 was affected by the heap overflow CVE-2019-15903.
353: <br>
354: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/024_expat.patch.sig">
355: A source code patch exists which remedies this problem.</a>
356: <p>
357:
1.28 tj 358: <li id="p025_unbound">
359: <strong>025: RELIABILITY FIX: October 5, 2019</strong>
360: <i>All architectures</i>
361: <br>
362: Specially crafted queries may crash unwind and unbound.
363: <br>
364: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/025_unbound.patch.sig">
365: A source code patch exists which remedies this problem.</a>
366: <p>
367:
368: <li id="p026_dhcpd">
369: <strong>026: SECURITY FIX: October 5, 2019</strong>
370: <i>All architectures</i>
371: <br>
372: dhcpd leaks 4 bytes of stack to the network.
373: <br>
374: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/026_dhcpd.patch.sig">
375: A source code patch exists which remedies this problem.</a>
376: <p>
377:
1.1 deraadt 378: </ul>
379:
380: <hr>