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