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