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