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