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