Annotation of www/errata63.html, Revision 1.25
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2: <html>
3: <head>
4: <title>OpenBSD 6.3 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/errata63.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.3 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>,
68: <a href="errata61.html">6.1</a>,
1.19 deraadt 69: <a href="errata62.html">6.2</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.3/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.3.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:
85: amd64, i386, arm64.
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 afresh1 96: <li id="p001_perl">
97: <font color="#009000">
98: <strong>001: SECURITY FIX: April 14, 2018</strong></font>
99: <i>All architectures</i>
100: <br>
101: Heap overflows exist in perl which can lead to segmentation faults,
102: crashes, and reading memory past the buffer.
103: <br>
104: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/001_perl.patch.sig">
105: A source code patch exists which remedies this problem.</a>
106: <p>
1.1 deraadt 107:
1.4 tj 108: <li id="p002_libtls">
1.3 tj 109: <font color="#009000">
110: <strong>002: RELIABILITY FIX: April 21, 2018</strong></font>
111: <i>All architectures</i>
112: <br>
1.4 tj 113: Additional data is inadvertently removed when private keys are cleared from
114: TLS configuration, which can prevent OCSP from functioning correctly.
1.3 tj 115: <br>
1.4 tj 116: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/002_libtls.patch.sig">
1.3 tj 117: A source code patch exists which remedies this problem.</a>
118: <p>
119:
1.4 tj 120: <li id="p003_arp">
1.3 tj 121: <font color="#009000">
122: <strong>003: RELIABILITY FIX: April 21, 2018</strong></font>
123: <i>All architectures</i>
124: <br>
1.4 tj 125: ARP replies could be sent on the wrong member of a bridge(4) interface.
1.3 tj 126: <br>
1.4 tj 127: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/003_arp.patch.sig">
1.3 tj 128: A source code patch exists which remedies this problem.</a>
129: <p>
130:
131: <li id="p004_gif">
132: <font color="#009000">
133: <strong>004: SECURITY FIX: April 21, 2018</strong></font>
134: <i>All architectures</i>
135: <br>
136: In the gif(4) interface, use the specified protocol for IPv6, plug
137: a mbuf leak and avoid a use after free.
138: <br>
139: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/004_gif.patch.sig">
140: A source code patch exists which remedies this problem.</a>
141: <p>
142:
143: <li id="p005_httpd">
144: <font color="#009000">
145: <strong>005: RELIABILITY FIX: April 21, 2018</strong></font>
146: <i>All architectures</i>
147: <br>
148: httpd can leak file descriptors when servicing range requests.
149: <br>
150: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/005_httpd.patch.sig">
151: A source code patch exists which remedies this problem.</a>
152: <p>
153:
1.5 tj 154: <li id="p006_ipseclen">
155: <font color="#009000">
156: <strong>006: RELIABILITY FIX: May 8, 2018</strong></font>
157: <i>All architectures</i>
158: <br>
159: Incorrect handling of fragmented IPsec packets could result in a system crash.
160: <br>
161: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/006_ipseclen.patch.sig">
162: A source code patch exists which remedies this problem.</a>
163: <p>
164:
165: <li id="p007_libcrypto">
166: <font color="#009000">
167: <strong>007: RELIABILITY FIX: May 8, 2018</strong></font>
168: <i>All architectures</i>
169: <br>
170: Incorrect checks in libcrypto can prevent Diffie-Hellman Exchange operations
171: from working.
172: <br>
173: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/007_libcrypto.patch.sig">
174: A source code patch exists which remedies this problem.</a>
175: <p>
176:
1.6 tj 177: <li id="p008_ipsecout">
178: <font color="#009000">
179: <strong>008: RELIABILITY FIX: May 17, 2018</strong></font>
180: <i>All architectures</i>
181: <br>
182: A malicious packet can cause a kernel crash when using IPsec over IPv6.
183: <br>
184: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/008_ipsecout.patch.sig">
185: A source code patch exists which remedies this problem.</a>
186: <p>
187:
1.7 tb 188: <li id="p009_libcrypto">
189: <font color="#009000">
190: <strong>009: SECURITY FIX: June 14, 2018</strong></font>
191: <i>All architectures</i>
192: <br>
193: DSA and ECDSA signature generation can potentially leak secret information
194: to a timing side-channel attack.
195: <br>
196: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/009_libcrypto.patch.sig">
197: A source code patch exists which remedies this problem.</a>
198: <p>
199:
1.8 tj 200: <li id="p010_intelfpu">
201: <font color="#009000">
202: <strong>010: SECURITY FIX: June 17, 2018</strong></font>
203: <i>amd64</i>
204: <br>
205: Intel CPUs speculatively access FPU registers even when the FPU is disabled,
206: so data (including AES keys) from previous contexts could be discovered
207: if using the lazy-save approach.
208: <br>
209: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/010_intelfpu.patch.sig">
210: A source code patch exists which remedies this problem.</a>
211: <p>
212:
1.9 afresh1 213: <li id="p011_perl">
214: <font color="#009000">
215: <strong>011: SECURITY FIX: June 21, 2018</strong></font>
216: <i>All architectures</i>
217: <br>
218: Perl's Archive::Tar module could be made to write files outside of
219: its working directory.
220: <br>
221: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/011_perl.patch.sig">
222: A source code patch exists which remedies this problem.</a>
223: <p>
224:
1.10 tj 225: <li id="p012_execsize">
226: <font color="#009000">
227: <strong>012: RELIABILITY FIX: July 25, 2018</strong></font>
228: <i>All architectures</i>
229: <br>
230: A regular user could trigger a kernel panic by executing an invalid
231: ELF binary.
232: <br>
233: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/012_execsize.patch.sig">
234: A source code patch exists which remedies this problem.</a>
235: <p>
236:
237: <li id="p013_ipsecexpire">
238: <font color="#009000">
239: <strong>013: RELIABILITY FIX: July 25, 2018</strong></font>
240: <i>All architectures</i>
241: <br>
242: When an IPsec key expired, the kernel could panic due to unfinished
243: timeout tasks.
244: <br>
245: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/013_ipsecexpire.patch.sig">
246: A source code patch exists which remedies this problem.</a>
247: <p>
248:
1.11 tj 249: <li id="p014_amdlfence">
250: <font color="#009000">
251: <strong>014: SECURITY FIX: July 31, 2018</strong></font>
252: <i>amd64 and i386</i>
253: <br>
254: On AMD CPUs, set a chicken bit which turns LFENCE into a serialization
255: instruction against speculation.
256: <br>
257: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/014_amdlfence.patch.sig">
258: A source code patch exists which remedies this problem.</a>
259: <p>
260:
261: <li id="p015_ioport">
262: <font color="#009000">
1.13 tj 263: <strong>015: SECURITY FIX: July 31, 2018</strong></font>
1.11 tj 264: <i>i386</i>
265: <br>
266: IO port permissions were incorrectly restricted.
267: <br>
268: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/015_ioport.patch.sig">
269: A source code patch exists which remedies this problem.</a>
270: <p>
271:
1.14 tj 272: <li id="p016_fpuinit">
273: <font color="#009000">
1.16 deraadt 274: <strong>016: RELIABILITY FIX: August 4, 2018</strong></font>
1.14 tj 275: <i>amd64</i>
276: <br>
277: Incorrect initialization of the FPU caused floating point exceptions
278: when running on Xen.
279: <br>
280: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/016_fpuinit.patch.sig">
281: A source code patch exists which remedies this problem.</a>
282: <p>
283:
1.17 tj 284: <li id="p017_fpufork">
285: <font color="#009000">
286: <strong>017: SECURITY FIX: August 24, 2018</strong></font>
287: <i>amd64</i>
288: <br>
289: State from the FPU of one userland process could be exposed to other processes.
290: <br>
291: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/017_fpufork.patch.sig">
292: A source code patch exists which remedies this problem.</a>
293: <p>
294:
295: <li id="p018_vmml1tf">
296: <font color="#009000">
297: <strong>018: SECURITY FIX: August 24, 2018</strong></font>
298: <i>amd64</i>
299: <br>
300: The Intel L1TF bug allows a vmm guest to read host memory.
301: Install the CPU firmware using fw_update(1) and apply this workaround.
302: <br>
303: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/018_vmml1tf.patch.sig">
304: A source code patch exists which remedies this problem.</a>
305: <p>
306:
1.18 tj 307: <li id="p019_ldtr">
308: <font color="#009000">
309: <strong>019: SECURITY FIX: September 21, 2018</strong></font>
310: <i>amd64</i>
311: <br>
312: On AMD CPUs, LDTR must be managed crossing between VMs.
313: <br>
314: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/019_ldtr.patch.sig">
315: A source code patch exists which remedies this problem.</a>
316: <p>
317:
1.20 tj 318: <li id="p020_xserver">
319: <font color="#009000">
320: <strong>020: SECURITY FIX: October 25, 2018</strong></font>
321: <i>All architectures</i>
322: <br>
323: The Xorg X server incorrectly validates certain options, allowing arbitrary
324: files to be overwritten.
325: As an immediate (temporary) workaround, the Xorg binary can be disabled
326: by running: <code>chmod u-s /usr/X11R6/bin/Xorg</code>
327: <br>
328: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/020_xserver.patch.sig">
329: A source code patch exists which remedies this problem.</a>
330: <p>
331:
1.21 tj 332: <li id="p021_syspatch">
333: <font color="#009000">
334: <strong>021: RELIABILITY FIX: November 2, 2018</strong></font>
335: <i>i386, amd64, arm64</i>
336: <br>
337: The syspatch utility incorrectly handles symbolic links.
338: <br>
339: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/021_syspatch.patch.sig">
340: A source code patch exists which remedies this problem.</a>
341: <p>
342:
1.22 tj 343: <li id="p022_blinding">
344: <font color="#009000">
345: <strong>022: SECURITY FIX: November 17, 2018</strong></font>
346: <i>All architectures</i>
347: <br>
348: Timing side channels may leak information about DSA and ECDSA private keys.
349: <br>
350: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/022_blinding.patch.sig">
351: A source code patch exists which remedies this problem.</a>
352: <p>
353:
354: <li id="p023_lockf">
355: <font color="#009000">
356: <strong>023: RELIABILITY FIX: November 17, 2018</strong></font>
357: <i>All architectures</i>
358: <br>
359: A recent change to POSIX file locks could cause incorrect results
360: during lock acquisition.
361: <br>
362: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/023_lockf.patch.sig">
363: A source code patch exists which remedies this problem.</a>
364: <p>
365:
1.23 tj 366: <li id="p024_perl">
367: <font color="#009000">
368: <strong>024: SECURITY FIX: November 29, 2018</strong></font>
369: <i>All architectures</i>
370: <br>
371: Various overflows exist in perl.
372: <br>
373: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/024_perl.patch.sig">
374: A source code patch exists which remedies this problem.</a>
375: <p>
376:
377: <li id="p025_uipc">
378: <font color="#009000">
379: <strong>025: RELIABILITY FIX: November 29, 2018</strong></font>
380: <i>All architectures</i>
381: <br>
382: UNIX domain sockets leak kernel memory with MSG_PEEK on SCM_RIGHTS, or can
383: attempt excessive memory allocations leading to a crash.
384: <br>
385: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/025_uipc.patch.sig">
386: A source code patch exists which remedies this problem.</a>
387: <p>
388:
1.24 tj 389: <li id="p026_recvwait">
390: <font color="#009000">
391: <strong>026: RELIABILITY FIX: December 20, 2018</strong></font>
392: <i>All architectures</i>
393: <br>
394: While recv(2) with the MSG_WAITALL flag was receiving control
395: messages from a socket, the kernel could panic.
396: <br>
397: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/026_recvwait.patch.sig">
398: A source code patch exists which remedies this problem.</a>
399: <p>
400:
1.25 ! tj 401: <li id="p027_pcbopts">
! 402: <font color="#009000">
! 403: <strong>027: SECURITY FIX: December 22, 2018</strong></font>
! 404: <i>All architectures</i>
! 405: <br>
! 406: The setsockopt(2) system call could overflow mbuf cluster kernel
! 407: memory by 4 bytes.
! 408: <br>
! 409: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/027_pcbopts.patch.sig">
! 410: A source code patch exists which remedies this problem.</a>
! 411: <p>
! 412:
1.1 deraadt 413: </ul>
414:
415: <hr>
416:
417: </body>
418: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to errata63.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www