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