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