Annotation of www/errata62.html, Revision 1.33
1.29 bentley 1: <!doctype html>
2: <html lang=en id=errata>
3: <meta charset=utf-8>
4:
1.1 deraadt 5: <title>OpenBSD 6.2 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/errata62.html">
10:
11: <!--
12: IMPORTANT REMINDER
13: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
14: -->
15:
1.29 bentley 16: <h2 id=OpenBSD>
1.1 deraadt 17: <a href="index.html">
1.29 bentley 18: <i>Open</i><b>BSD</b></a>
19: 6.2 Errata
1.1 deraadt 20: </h2>
21: <hr>
22:
23: For errata on a certain release, click below:<br>
1.31 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.31 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.31 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>,
1.11 deraadt 67: <a href="errata61.html">6.1</a>,
1.26 deraadt 68: <a href="errata63.html">6.3</a>,
1.28 deraadt 69: <a href="errata64.html">6.4</a>,
1.30 deraadt 70: <a href="errata65.html">6.5</a>,
1.32 deraadt 71: <a href="errata66.html">6.6</a>,
1.33 ! 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
79: <a href="https://man.openbsd.org/OpenBSD-6.2/signify.1">signify(1)</a> tool and contains
80: usage instructions.
81: All the following patches are also available in one
82: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2.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:
1.3 tj 88: amd64, i386, arm64.
1.1 deraadt 89:
90: <p>
91: Patches for supported releases are also incorporated into the
1.27 tj 92: <a href="stable.html">-stable branch</a>.
1.1 deraadt 93:
94: <hr>
95:
96: <ul>
97:
1.2 bluhm 98: <li id="p001_tcb_invalid">
1.29 bentley 99: <strong>001: RELIABILITY FIX: October 13, 2017</strong>
1.2 bluhm 100: <i>amd64</i>
101: <br>
102: A local user could trigger a kernel panic by using an invalid TCB value.
103: <br>
104: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/001_tcb_invalid.patch.sig">
1.3 tj 105: A source code patch exists which remedies this problem.</a>
106: <p>
107:
108: <li id="p002_fktrace">
1.29 bentley 109: <strong>002: SECURITY FIX: December 1, 2017</strong>
1.3 tj 110: <i>All architectures</i>
111: <br>
112: The fktrace(2) system call had insufficient security checks.
113: <br>
114: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/002_fktrace.patch.sig">
1.2 bluhm 115: A source code patch exists which remedies this problem.</a>
116: <p>
1.1 deraadt 117:
1.4 tj 118: <li id="p003_mpls">
1.29 bentley 119: <strong>003: RELIABILITY FIX: December 10, 2017</strong>
1.4 tj 120: <i>All architectures</i>
121: <br>
122: A number of bugs were discovered in the MPLS stack that can be used to
123: remotely trigger kernel crashes.
124: <br>
125: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/003_mpls.patch.sig">
126: A source code patch exists which remedies this problem.</a>
127: <p>
128:
1.5 tj 129: <li id="p004_libssl">
1.29 bentley 130: <strong>004: RELIABILITY FIX: January 14, 2018</strong>
1.5 tj 131: <i>All architectures</i>
132: <br>
133: An incorrect TLS extensions block is generated when no extensions are present,
134: which can result in handshake failures.
135: <br>
136: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/004_libssl.patch.sig">
137: A source code patch exists which remedies this problem.</a>
138: <p>
139:
1.6 tj 140: <li id="p005_ahopts">
1.29 bentley 141: <strong>005: RELIABILITY FIX: February 2, 2018</strong>
1.6 tj 142: <i>All architectures</i>
143: <br>
144: Specially crafted IPsec AH packets with IP options or IPv6 extension
145: headers could crash or hang the kernel.
146: <br>
147: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/005_ahopts.patch.sig">
148: A source code patch exists which remedies this problem.</a>
149: <p>
150:
151: <li id="p006_prevhdr">
1.29 bentley 152: <strong>006: RELIABILITY FIX: February 2, 2018</strong>
1.6 tj 153: <i>All architectures</i>
154: <br>
155: Processing IPv6 fragments could incorrectly access memory of an mbuf
156: chain that is not within an mbuf. This may crash the kernel.
157: <br>
158: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/006_prevhdr.patch.sig">
159: A source code patch exists which remedies this problem.</a>
160: <p>
161:
162: <li id="p007_etherip">
1.29 bentley 163: <strong>007: SECURITY FIX: February 2, 2018</strong>
1.6 tj 164: <i>All architectures</i>
165: <br>
166: If the EtherIP tunnel protocol was disabled, IPv6 packets were not
167: discarded properly. This causes a double free in the kernel.
168: <br>
169: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/007_etherip.patch.sig">
170: A source code patch exists which remedies this problem.</a>
171: <p>
172:
1.7 tj 173: <li id="p008_unbound">
1.29 bentley 174: <strong>008: SECURITY FIX: February 8, 2018</strong>
1.7 tj 175: <i>All architectures</i>
176: <br>
177: A flaw was found in the way unbound validated wildcard-synthesized
178: NSEC records. An improperly validated wildcard NSEC record could be
179: used to prove the non-existence (NXDOMAIN answer) of an existing
180: wildcard record, or trick unbound into accepting a NODATA proof.
181: <br>
182: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/008_unbound.patch.sig">
183: A source code patch exists which remedies this problem.</a>
184: <p>
185:
1.9 tj 186: <li id="p009_meltdown">
1.29 bentley 187: <strong>009: SECURITY FIX: March 1, 2018</strong>
1.9 tj 188: <i>amd64</i>
189: <br>
190: Intel CPUs contain a speculative execution flaw called Meltdown which
191: allows userspace programs to access kernel memory.
192: <br>
193: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/009_meltdown.patch.sig">
194: A complex workaround solves this problem.</a>
195: <p>
196:
1.10 tj 197: <li id="p010_ahauth">
1.29 bentley 198: <strong>010: RELIABILITY FIX: March 20, 2018</strong>
1.10 tj 199: <i>All architectures</i>
200: <br>
201: The IPsec AH header could be longer than the network packet, resulting in
202: a kernel crash.
203: <br>
204: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/010_ahauth.patch.sig">
205: A source code patch exists which remedies this problem.</a>
206: <p>
207:
1.12 afresh1 208: <li id="p011_perl">
1.29 bentley 209: <strong>011: SECURITY FIX: April 14, 2018</strong>
1.12 afresh1 210: <i>All architectures</i>
211: <br>
212: Heap overflows exist in perl which can lead to segmentation faults,
213: crashes, and reading memory past the buffer.
214: <br>
215: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/011_perl.patch.sig">
216: A source code patch exists which remedies this problem.</a>
217: <p>
218:
1.13 tj 219: <li id="p012_httpd">
1.29 bentley 220: <strong>012: RELIABILITY FIX: April 21, 2018</strong>
1.13 tj 221: <i>All architectures</i>
222: <br>
223: httpd can leak file descriptors when servicing range requests.
224: <br>
225: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/012_httpd.patch.sig">
226: A source code patch exists which remedies this problem.</a>
227: <p>
228:
1.14 tj 229: <li id="p013_ipseclen">
1.29 bentley 230: <strong>013: RELIABILITY FIX: May 8, 2018</strong>
1.14 tj 231: <i>All architectures</i>
232: <br>
233: Incorrect handling of fragmented IPsec packets could result in a system crash.
234: <br>
235: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/013_ipseclen.patch.sig">
236: A source code patch exists which remedies this problem.</a>
237: <p>
238:
1.15 tj 239: <li id="p014_ipsecout">
1.29 bentley 240: <strong>014: RELIABILITY FIX: May 17, 2018</strong>
1.15 tj 241: <i>All architectures</i>
242: <br>
243: A malicious packet can cause a kernel crash when using IPsec over IPv6.
244: <br>
245: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/014_ipsecout.patch.sig">
246: A source code patch exists which remedies this problem.</a>
247: <p>
248:
1.16 tb 249: <li id="p015_libcrypto">
1.29 bentley 250: <strong>015: SECURITY FIX: June 14, 2018</strong>
1.16 tb 251: <i>All architectures</i>
252: <br>
253: DSA and ECDSA signature generation can potentially leak secret information
254: to a timing side-channel attack.
255: <br>
256: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/015_libcrypto.patch.sig">
257: A source code patch exists which remedies this problem.</a>
258: <p>
259:
1.17 afresh1 260: <li id="p016_perl">
1.29 bentley 261: <strong>016: SECURITY FIX: June 21, 2018</strong>
1.17 afresh1 262: <i>All architectures</i>
263: <br>
264: Perl's Archive::Tar module could be made to write files outside of
265: its working directory.
266: <br>
267: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/016_perl.patch.sig">
268: A source code patch exists which remedies this problem.</a>
269: <p>
270:
1.18 tj 271: <li id="p017_intelfpu">
1.29 bentley 272: <strong>017: SECURITY FIX: June 21, 2018</strong>
1.18 tj 273: <i>amd64</i>
274: <br>
275: Intel CPUs speculatively access FPU registers even when the FPU is disabled,
276: so data (including AES keys) from previous contexts could be discovered
277: if using the lazy-save approach.
278: <br>
279: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/017_intelfpu.patch.sig">
280: A source code patch exists which remedies this problem.</a>
281: <p>
282:
1.19 tj 283: <li id="p018_execsize">
1.29 bentley 284: <strong>018: RELIABILITY FIX: July 25, 2018</strong>
1.19 tj 285: <i>All architectures</i>
286: <br>
287: A regular user could trigger a kernel panic by executing an invalid
288: ELF binary.
289: <br>
290: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/018_execsize.patch.sig">
291: A source code patch exists which remedies this problem.</a>
292: <p>
293:
1.20 tj 294: <li id="p019_amdlfence">
1.29 bentley 295: <strong>019: SECURITY FIX: July 31, 2018</strong>
1.20 tj 296: <i>amd64 and i386</i>
297: <br>
298: On AMD CPUs, set a chicken bit which turns LFENCE into a serialization
299: instruction against speculation.
300: <br>
301: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/019_amdlfence.patch.sig">
302: A source code patch exists which remedies this problem.</a>
303: <p>
304:
305: <li id="p020_ioport">
1.29 bentley 306: <strong>020: SECURITY FIX: July 31, 2018</strong>
1.20 tj 307: <i>i386</i>
308: <br>
309: IO port permissions were incorrectly restricted.
310: <br>
311: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/020_ioport.patch.sig">
312: A source code patch exists which remedies this problem.</a>
313: <p>
314:
1.21 tj 315: <li id="p021_fpuinit">
1.29 bentley 316: <strong>021: RELIABILITY FIX: August 4, 2018</strong>
1.21 tj 317: <i>amd64</i>
318: <br>
319: Incorrect initialization of the FPU caused floating point exceptions
320: when running on Xen.
321: <br>
322: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/021_fpuinit.patch.sig">
323: A source code patch exists which remedies this problem.</a>
324: <p>
325:
1.24 tj 326: <li id="p022_fpufork">
1.29 bentley 327: <strong>022: SECURITY FIX: August 24, 2018</strong>
1.24 tj 328: <i>amd64</i>
329: <br>
330: State from the FPU of one userland process could be exposed to other processes.
331: <br>
332: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/022_fpufork.patch.sig">
333: A source code patch exists which remedies this problem.</a>
334: <p>
335:
336: <li id="p023_vmml1tf">
1.29 bentley 337: <strong>023: SECURITY FIX: August 24, 2018</strong>
1.24 tj 338: <i>amd64</i>
339: <br>
340: The Intel L1TF bug allows a vmm guest to read host memory.
341: Install the CPU firmware using fw_update(1), and apply this workaround.
342: <br>
343: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/023_vmml1tf.patch.sig">
344: A source code patch exists which remedies this problem.</a>
345: <p>
346:
1.25 tj 347: <li id="p024_ldtr">
1.29 bentley 348: <strong>024: SECURITY FIX: September 21, 2018</strong>
1.25 tj 349: <i>amd64</i>
350: <br>
351: On AMD CPUs, LDTR must be managed crossing between VMs.
352: <br>
353: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/024_ldtr.patch.sig">
354: A source code patch exists which remedies this problem.</a>
355: <p>
356:
1.1 deraadt 357: </ul>
358:
359: <hr>