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