Annotation of www/errata62.html, Revision 1.26
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2: <html>
3: <head>
4: <title>OpenBSD 6.2 Errata</title>
5: <meta name="description" content="the OpenBSD errata page">
6: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
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: </head>
11:
12: <!--
13: IMPORTANT REMINDER
14: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
15: -->
16: <body bgcolor="#ffffff" text="#000000" link="#23238E">
17:
18: <h2>
19: <a href="index.html">
20: <font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>
21: <font color="#e00000">6.2 Errata</font>
22: </h2>
23: <hr>
24:
25: For errata on a certain release, click below:<br>
26: <a href="errata21.html">2.1</a>,
27: <a href="errata22.html">2.2</a>,
28: <a href="errata23.html">2.3</a>,
29: <a href="errata24.html">2.4</a>,
30: <a href="errata25.html">2.5</a>,
31: <a href="errata26.html">2.6</a>,
32: <a href="errata27.html">2.7</a>,
33: <a href="errata28.html">2.8</a>,
34: <a href="errata29.html">2.9</a>,
35: <a href="errata30.html">3.0</a>,
36: <a href="errata31.html">3.1</a>,
37: <a href="errata32.html">3.2</a>,
38: <a href="errata33.html">3.3</a>,
39: <a href="errata34.html">3.4</a>,
40: <a href="errata35.html">3.5</a>,
41: <a href="errata36.html">3.6</a>,
42: <br>
43: <a href="errata37.html">3.7</a>,
44: <a href="errata38.html">3.8</a>,
45: <a href="errata39.html">3.9</a>,
46: <a href="errata40.html">4.0</a>,
47: <a href="errata41.html">4.1</a>,
48: <a href="errata42.html">4.2</a>,
49: <a href="errata43.html">4.3</a>,
50: <a href="errata44.html">4.4</a>,
51: <a href="errata45.html">4.5</a>,
52: <a href="errata46.html">4.6</a>,
53: <a href="errata47.html">4.7</a>,
54: <a href="errata48.html">4.8</a>,
55: <a href="errata49.html">4.9</a>,
56: <a href="errata50.html">5.0</a>,
57: <a href="errata51.html">5.1</a>,
58: <a href="errata52.html">5.2</a>,
59: <br>
60: <a href="errata53.html">5.3</a>,
61: <a href="errata54.html">5.4</a>,
62: <a href="errata55.html">5.5</a>,
63: <a href="errata56.html">5.6</a>,
64: <a href="errata57.html">5.7</a>,
65: <a href="errata58.html">5.8</a>,
66: <a href="errata59.html">5.9</a>,
67: <a href="errata60.html">6.0</a>,
1.11 deraadt 68: <a href="errata61.html">6.1</a>,
1.26 ! deraadt 69: <a href="errata63.html">6.3</a>,
! 70: <a href="errata64.html">6.4</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
89: <a href="stable.html">-stable branch</a>, which is maintained for one year
90: after release.
91:
92: <hr>
93:
94: <ul>
95:
1.2 bluhm 96: <li id="p001_tcb_invalid">
97: <font color="#009000">
98: <strong>001: RELIABILITY FIX: October 13, 2017</strong></font>
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">
108: <font color="#009000">
109: <strong>002: SECURITY FIX: December 1, 2017</strong></font>
110: <i>All architectures</i>
111: <br>
112: The fktrace(2) system call had insufficient security checks.
113: <br>
114: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/002_fktrace.patch.sig">
1.2 bluhm 115: A source code patch exists which remedies this problem.</a>
116: <p>
1.1 deraadt 117:
1.4 tj 118: <li id="p003_mpls">
119: <font color="#009000">
120: <strong>003: RELIABILITY FIX: December 10, 2017</strong></font>
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">
131: <font color="#009000">
132: <strong>004: RELIABILITY FIX: January 14, 2018</strong></font>
133: <i>All architectures</i>
134: <br>
135: An incorrect TLS extensions block is generated when no extensions are present,
136: which can result in handshake failures.
137: <br>
138: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/004_libssl.patch.sig">
139: A source code patch exists which remedies this problem.</a>
140: <p>
141:
1.6 tj 142: <li id="p005_ahopts">
143: <font color="#009000">
144: <strong>005: RELIABILITY FIX: February 2, 2018</strong></font>
145: <i>All architectures</i>
146: <br>
147: Specially crafted IPsec AH packets with IP options or IPv6 extension
148: headers could crash or hang the kernel.
149: <br>
150: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/005_ahopts.patch.sig">
151: A source code patch exists which remedies this problem.</a>
152: <p>
153:
154: <li id="p006_prevhdr">
155: <font color="#009000">
156: <strong>006: RELIABILITY FIX: February 2, 2018</strong></font>
157: <i>All architectures</i>
158: <br>
159: Processing IPv6 fragments could incorrectly access memory of an mbuf
160: chain that is not within an mbuf. This may crash the kernel.
161: <br>
162: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/006_prevhdr.patch.sig">
163: A source code patch exists which remedies this problem.</a>
164: <p>
165:
166: <li id="p007_etherip">
167: <font color="#009000">
168: <strong>007: SECURITY FIX: February 2, 2018</strong></font>
169: <i>All architectures</i>
170: <br>
171: If the EtherIP tunnel protocol was disabled, IPv6 packets were not
172: discarded properly. This causes a double free in the kernel.
173: <br>
174: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/007_etherip.patch.sig">
175: A source code patch exists which remedies this problem.</a>
176: <p>
177:
1.7 tj 178: <li id="p008_unbound">
179: <font color="#009000">
1.8 tj 180: <strong>008: SECURITY FIX: February 8, 2018</strong></font>
1.7 tj 181: <i>All architectures</i>
182: <br>
183: A flaw was found in the way unbound validated wildcard-synthesized
184: NSEC records. An improperly validated wildcard NSEC record could be
185: used to prove the non-existence (NXDOMAIN answer) of an existing
186: wildcard record, or trick unbound into accepting a NODATA proof.
187: <br>
188: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/008_unbound.patch.sig">
189: A source code patch exists which remedies this problem.</a>
190: <p>
191:
1.9 tj 192: <li id="p009_meltdown">
193: <font color="#009000">
194: <strong>009: SECURITY FIX: March 1, 2018</strong></font>
195: <i>amd64</i>
196: <br>
197: Intel CPUs contain a speculative execution flaw called Meltdown which
198: allows userspace programs to access kernel memory.
199: <br>
200: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/009_meltdown.patch.sig">
201: A complex workaround solves this problem.</a>
202: <p>
203:
1.10 tj 204: <li id="p010_ahauth">
205: <font color="#009000">
206: <strong>010: RELIABILITY FIX: March 20, 2018</strong></font>
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">
217: <font color="#009000">
218: <strong>011: SECURITY FIX: April 14, 2018</strong></font>
219: <i>All architectures</i>
220: <br>
221: Heap overflows exist in perl which can lead to segmentation faults,
222: crashes, and reading memory past the buffer.
223: <br>
224: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/011_perl.patch.sig">
225: A source code patch exists which remedies this problem.</a>
226: <p>
227:
1.13 tj 228: <li id="p012_httpd">
229: <font color="#009000">
230: <strong>012: RELIABILITY FIX: April 21, 2018</strong></font>
231: <i>All architectures</i>
232: <br>
233: httpd can leak file descriptors when servicing range requests.
234: <br>
235: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/012_httpd.patch.sig">
236: A source code patch exists which remedies this problem.</a>
237: <p>
238:
1.14 tj 239: <li id="p013_ipseclen">
240: <font color="#009000">
241: <strong>013: RELIABILITY FIX: May 8, 2018</strong></font>
242: <i>All architectures</i>
243: <br>
244: Incorrect handling of fragmented IPsec packets could result in a system crash.
245: <br>
246: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/013_ipseclen.patch.sig">
247: A source code patch exists which remedies this problem.</a>
248: <p>
249:
1.15 tj 250: <li id="p014_ipsecout">
251: <font color="#009000">
252: <strong>014: RELIABILITY FIX: May 17, 2018</strong></font>
253: <i>All architectures</i>
254: <br>
255: A malicious packet can cause a kernel crash when using IPsec over IPv6.
256: <br>
257: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/014_ipsecout.patch.sig">
258: A source code patch exists which remedies this problem.</a>
259: <p>
260:
1.16 tb 261: <li id="p015_libcrypto">
262: <font color="#009000">
263: <strong>015: SECURITY FIX: June 14, 2018</strong></font>
264: <i>All architectures</i>
265: <br>
266: DSA and ECDSA signature generation can potentially leak secret information
267: to a timing side-channel attack.
268: <br>
269: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/015_libcrypto.patch.sig">
270: A source code patch exists which remedies this problem.</a>
271: <p>
272:
1.17 afresh1 273: <li id="p016_perl">
274: <font color="#009000">
275: <strong>016: SECURITY FIX: June 21, 2018</strong></font>
276: <i>All architectures</i>
277: <br>
278: Perl's Archive::Tar module could be made to write files outside of
279: its working directory.
280: <br>
281: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/016_perl.patch.sig">
282: A source code patch exists which remedies this problem.</a>
283: <p>
284:
1.18 tj 285: <li id="p017_intelfpu">
286: <font color="#009000">
287: <strong>017: SECURITY FIX: June 21, 2018</strong></font>
288: <i>amd64</i>
289: <br>
290: Intel CPUs speculatively access FPU registers even when the FPU is disabled,
291: so data (including AES keys) from previous contexts could be discovered
292: if using the lazy-save approach.
293: <br>
294: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/017_intelfpu.patch.sig">
295: A source code patch exists which remedies this problem.</a>
296: <p>
297:
1.19 tj 298: <li id="p018_execsize">
299: <font color="#009000">
300: <strong>018: RELIABILITY FIX: July 25, 2018</strong></font>
301: <i>All architectures</i>
302: <br>
303: A regular user could trigger a kernel panic by executing an invalid
304: ELF binary.
305: <br>
306: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/018_execsize.patch.sig">
307: A source code patch exists which remedies this problem.</a>
308: <p>
309:
1.20 tj 310: <li id="p019_amdlfence">
311: <font color="#009000">
312: <strong>019: SECURITY FIX: July 31, 2018</strong></font>
313: <i>amd64 and i386</i>
314: <br>
315: On AMD CPUs, set a chicken bit which turns LFENCE into a serialization
316: instruction against speculation.
317: <br>
318: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/019_amdlfence.patch.sig">
319: A source code patch exists which remedies this problem.</a>
320: <p>
321:
322: <li id="p020_ioport">
323: <font color="#009000">
324: <strong>020: SECURITY FIX: July 31, 2018</strong></font>
325: <i>i386</i>
326: <br>
327: IO port permissions were incorrectly restricted.
328: <br>
329: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/020_ioport.patch.sig">
330: A source code patch exists which remedies this problem.</a>
331: <p>
332:
1.21 tj 333: <li id="p021_fpuinit">
334: <font color="#009000">
1.23 deraadt 335: <strong>021: RELIABILITY FIX: August 4, 2018</strong></font>
1.21 tj 336: <i>amd64</i>
337: <br>
338: Incorrect initialization of the FPU caused floating point exceptions
339: when running on Xen.
340: <br>
341: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/021_fpuinit.patch.sig">
342: A source code patch exists which remedies this problem.</a>
343: <p>
344:
1.24 tj 345: <li id="p022_fpufork">
346: <font color="#009000">
347: <strong>022: SECURITY FIX: August 24, 2018</strong></font>
348: <i>amd64</i>
349: <br>
350: State from the FPU of one userland process could be exposed to other processes.
351: <br>
352: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/022_fpufork.patch.sig">
353: A source code patch exists which remedies this problem.</a>
354: <p>
355:
356: <li id="p023_vmml1tf">
357: <font color="#009000">
358: <strong>023: SECURITY FIX: August 24, 2018</strong></font>
359: <i>amd64</i>
360: <br>
361: The Intel L1TF bug allows a vmm guest to read host memory.
362: Install the CPU firmware using fw_update(1), and apply this workaround.
363: <br>
364: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/023_vmml1tf.patch.sig">
365: A source code patch exists which remedies this problem.</a>
366: <p>
367:
1.25 tj 368: <li id="p024_ldtr">
369: <font color="#009000">
370: <strong>024: SECURITY FIX: September 21, 2018</strong></font>
371: <i>amd64</i>
372: <br>
373: On AMD CPUs, LDTR must be managed crossing between VMs.
374: <br>
375: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.2/common/024_ldtr.patch.sig">
376: A source code patch exists which remedies this problem.</a>
377: <p>
378:
1.1 deraadt 379: </ul>
380:
381: <hr>
382:
383: </body>
384: </html>
![[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