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