Annotation of www/errata63.html, Revision 1.40
1.35 bentley 1: <!doctype html>
2: <html lang=en id=errata>
3: <meta charset=utf-8>
4:
1.1 deraadt 5: <title>OpenBSD 6.3 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/errata63.html">
10:
11: <!--
12: IMPORTANT REMINDER
13: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
14: -->
15:
1.35 bentley 16: <h2 id=OpenBSD>
1.1 deraadt 17: <a href="index.html">
1.35 bentley 18: <i>Open</i><b>BSD</b></a>
19: 6.3 Errata
1.1 deraadt 20: </h2>
21: <hr>
22:
23: For errata on a certain release, click below:<br>
1.38 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.38 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.38 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>,
67: <a href="errata61.html">6.1</a>,
1.19 deraadt 68: <a href="errata62.html">6.2</a>,
1.32 deraadt 69: <a href="errata64.html">6.4</a>,
1.37 deraadt 70: <a href="errata65.html">6.5</a>,
1.39 deraadt 71: <a href="errata66.html">6.6</a>,
1.40 ! deraadt 72: <a href="errata67.html">6.7</a>,
! 73: <a href="errata68.html">6.8</a>.
1.1 deraadt 74: <hr>
75:
76: <p>
77: Patches for the OpenBSD base system are distributed as unified diffs.
78: Each patch is cryptographically signed with the
79: <a href="https://man.openbsd.org/OpenBSD-6.3/signify.1">signify(1)</a> tool and contains
80: usage instructions.
81: All the following patches are also available in one
82: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3.tar.gz">tar.gz file</a>
83: for convenience.
84:
85: <p>
86: Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
87: utility can be used to apply binary updates on the following architectures:
88: amd64, i386, arm64.
89:
90: <p>
91: Patches for supported releases are also incorporated into the
1.33 tj 92: <a href="stable.html">-stable branch</a>.
1.1 deraadt 93:
94: <hr>
95:
96: <ul>
97:
1.2 afresh1 98: <li id="p001_perl">
1.35 bentley 99: <strong>001: SECURITY FIX: April 14, 2018</strong>
1.2 afresh1 100: <i>All architectures</i>
101: <br>
102: Heap overflows exist in perl which can lead to segmentation faults,
103: crashes, and reading memory past the buffer.
104: <br>
105: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/001_perl.patch.sig">
106: A source code patch exists which remedies this problem.</a>
107: <p>
1.1 deraadt 108:
1.4 tj 109: <li id="p002_libtls">
1.35 bentley 110: <strong>002: RELIABILITY FIX: April 21, 2018</strong>
1.3 tj 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.35 bentley 121: <strong>003: RELIABILITY FIX: April 21, 2018</strong>
1.3 tj 122: <i>All architectures</i>
123: <br>
1.4 tj 124: ARP replies could be sent on the wrong member of a bridge(4) interface.
1.3 tj 125: <br>
1.4 tj 126: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/003_arp.patch.sig">
1.3 tj 127: A source code patch exists which remedies this problem.</a>
128: <p>
129:
130: <li id="p004_gif">
1.35 bentley 131: <strong>004: SECURITY FIX: April 21, 2018</strong>
1.3 tj 132: <i>All architectures</i>
133: <br>
134: In the gif(4) interface, use the specified protocol for IPv6, plug
135: a mbuf leak and avoid a use after free.
136: <br>
137: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/004_gif.patch.sig">
138: A source code patch exists which remedies this problem.</a>
139: <p>
140:
141: <li id="p005_httpd">
1.35 bentley 142: <strong>005: RELIABILITY FIX: April 21, 2018</strong>
1.3 tj 143: <i>All architectures</i>
144: <br>
145: httpd can leak file descriptors when servicing range requests.
146: <br>
147: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/005_httpd.patch.sig">
148: A source code patch exists which remedies this problem.</a>
149: <p>
150:
1.5 tj 151: <li id="p006_ipseclen">
1.35 bentley 152: <strong>006: RELIABILITY FIX: May 8, 2018</strong>
1.5 tj 153: <i>All architectures</i>
154: <br>
155: Incorrect handling of fragmented IPsec packets could result in a system crash.
156: <br>
157: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/006_ipseclen.patch.sig">
158: A source code patch exists which remedies this problem.</a>
159: <p>
160:
161: <li id="p007_libcrypto">
1.35 bentley 162: <strong>007: RELIABILITY FIX: May 8, 2018</strong>
1.5 tj 163: <i>All architectures</i>
164: <br>
165: Incorrect checks in libcrypto can prevent Diffie-Hellman Exchange operations
166: from working.
167: <br>
168: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/007_libcrypto.patch.sig">
169: A source code patch exists which remedies this problem.</a>
170: <p>
171:
1.6 tj 172: <li id="p008_ipsecout">
1.35 bentley 173: <strong>008: RELIABILITY FIX: May 17, 2018</strong>
1.6 tj 174: <i>All architectures</i>
175: <br>
176: A malicious packet can cause a kernel crash when using IPsec over IPv6.
177: <br>
178: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/008_ipsecout.patch.sig">
179: A source code patch exists which remedies this problem.</a>
180: <p>
181:
1.7 tb 182: <li id="p009_libcrypto">
1.35 bentley 183: <strong>009: SECURITY FIX: June 14, 2018</strong>
1.7 tb 184: <i>All architectures</i>
185: <br>
186: DSA and ECDSA signature generation can potentially leak secret information
187: to a timing side-channel attack.
188: <br>
189: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/009_libcrypto.patch.sig">
190: A source code patch exists which remedies this problem.</a>
191: <p>
192:
1.8 tj 193: <li id="p010_intelfpu">
1.35 bentley 194: <strong>010: SECURITY FIX: June 17, 2018</strong>
1.8 tj 195: <i>amd64</i>
196: <br>
197: Intel CPUs speculatively access FPU registers even when the FPU is disabled,
198: so data (including AES keys) from previous contexts could be discovered
199: if using the lazy-save approach.
200: <br>
201: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/010_intelfpu.patch.sig">
202: A source code patch exists which remedies this problem.</a>
203: <p>
204:
1.9 afresh1 205: <li id="p011_perl">
1.35 bentley 206: <strong>011: SECURITY FIX: June 21, 2018</strong>
1.9 afresh1 207: <i>All architectures</i>
208: <br>
209: Perl's Archive::Tar module could be made to write files outside of
210: its working directory.
211: <br>
212: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/011_perl.patch.sig">
213: A source code patch exists which remedies this problem.</a>
214: <p>
215:
1.10 tj 216: <li id="p012_execsize">
1.35 bentley 217: <strong>012: RELIABILITY FIX: July 25, 2018</strong>
1.10 tj 218: <i>All architectures</i>
219: <br>
220: A regular user could trigger a kernel panic by executing an invalid
221: ELF binary.
222: <br>
223: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/012_execsize.patch.sig">
224: A source code patch exists which remedies this problem.</a>
225: <p>
226:
227: <li id="p013_ipsecexpire">
1.35 bentley 228: <strong>013: RELIABILITY FIX: July 25, 2018</strong>
1.10 tj 229: <i>All architectures</i>
230: <br>
231: When an IPsec key expired, the kernel could panic due to unfinished
232: timeout tasks.
233: <br>
234: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/013_ipsecexpire.patch.sig">
235: A source code patch exists which remedies this problem.</a>
236: <p>
237:
1.11 tj 238: <li id="p014_amdlfence">
1.35 bentley 239: <strong>014: SECURITY FIX: July 31, 2018</strong>
1.11 tj 240: <i>amd64 and i386</i>
241: <br>
242: On AMD CPUs, set a chicken bit which turns LFENCE into a serialization
243: instruction against speculation.
244: <br>
245: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/014_amdlfence.patch.sig">
246: A source code patch exists which remedies this problem.</a>
247: <p>
248:
249: <li id="p015_ioport">
1.35 bentley 250: <strong>015: SECURITY FIX: July 31, 2018</strong>
1.11 tj 251: <i>i386</i>
252: <br>
253: IO port permissions were incorrectly restricted.
254: <br>
255: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/015_ioport.patch.sig">
256: A source code patch exists which remedies this problem.</a>
257: <p>
258:
1.14 tj 259: <li id="p016_fpuinit">
1.35 bentley 260: <strong>016: RELIABILITY FIX: August 4, 2018</strong>
1.14 tj 261: <i>amd64</i>
262: <br>
263: Incorrect initialization of the FPU caused floating point exceptions
264: when running on Xen.
265: <br>
266: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/016_fpuinit.patch.sig">
267: A source code patch exists which remedies this problem.</a>
268: <p>
269:
1.17 tj 270: <li id="p017_fpufork">
1.35 bentley 271: <strong>017: SECURITY FIX: August 24, 2018</strong>
1.17 tj 272: <i>amd64</i>
273: <br>
274: State from the FPU of one userland process could be exposed to other processes.
275: <br>
276: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/017_fpufork.patch.sig">
277: A source code patch exists which remedies this problem.</a>
278: <p>
279:
280: <li id="p018_vmml1tf">
1.35 bentley 281: <strong>018: SECURITY FIX: August 24, 2018</strong>
1.17 tj 282: <i>amd64</i>
283: <br>
284: The Intel L1TF bug allows a vmm guest to read host memory.
285: Install the CPU firmware using fw_update(1) and apply this workaround.
286: <br>
287: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/018_vmml1tf.patch.sig">
288: A source code patch exists which remedies this problem.</a>
289: <p>
290:
1.18 tj 291: <li id="p019_ldtr">
1.35 bentley 292: <strong>019: SECURITY FIX: September 21, 2018</strong>
1.18 tj 293: <i>amd64</i>
294: <br>
295: On AMD CPUs, LDTR must be managed crossing between VMs.
296: <br>
297: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/019_ldtr.patch.sig">
298: A source code patch exists which remedies this problem.</a>
299: <p>
300:
1.20 tj 301: <li id="p020_xserver">
1.35 bentley 302: <strong>020: SECURITY FIX: October 25, 2018</strong>
1.20 tj 303: <i>All architectures</i>
304: <br>
1.36 deraadt 305: The Xorg X server incorrectly validates certain options, allowing arbitrary
1.20 tj 306: files to be overwritten.
307: As an immediate (temporary) workaround, the Xorg binary can be disabled
308: by running: <code>chmod u-s /usr/X11R6/bin/Xorg</code>
309: <br>
310: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/020_xserver.patch.sig">
311: A source code patch exists which remedies this problem.</a>
312: <p>
313:
1.21 tj 314: <li id="p021_syspatch">
1.35 bentley 315: <strong>021: RELIABILITY FIX: November 2, 2018</strong>
1.21 tj 316: <i>i386, amd64, arm64</i>
317: <br>
318: The syspatch utility incorrectly handles symbolic links.
319: <br>
320: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/021_syspatch.patch.sig">
321: A source code patch exists which remedies this problem.</a>
322: <p>
323:
1.22 tj 324: <li id="p022_blinding">
1.35 bentley 325: <strong>022: SECURITY FIX: November 17, 2018</strong>
1.22 tj 326: <i>All architectures</i>
327: <br>
328: Timing side channels may leak information about DSA and ECDSA private keys.
329: <br>
330: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/022_blinding.patch.sig">
331: A source code patch exists which remedies this problem.</a>
332: <p>
333:
334: <li id="p023_lockf">
1.35 bentley 335: <strong>023: RELIABILITY FIX: November 17, 2018</strong>
1.22 tj 336: <i>All architectures</i>
337: <br>
338: A recent change to POSIX file locks could cause incorrect results
339: during lock acquisition.
340: <br>
341: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/023_lockf.patch.sig">
342: A source code patch exists which remedies this problem.</a>
343: <p>
344:
1.23 tj 345: <li id="p024_perl">
1.35 bentley 346: <strong>024: SECURITY FIX: November 29, 2018</strong>
1.23 tj 347: <i>All architectures</i>
348: <br>
349: Various overflows exist in perl.
350: <br>
351: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/024_perl.patch.sig">
352: A source code patch exists which remedies this problem.</a>
353: <p>
354:
355: <li id="p025_uipc">
1.35 bentley 356: <strong>025: RELIABILITY FIX: November 29, 2018</strong>
1.23 tj 357: <i>All architectures</i>
358: <br>
359: UNIX domain sockets leak kernel memory with MSG_PEEK on SCM_RIGHTS, or can
360: attempt excessive memory allocations leading to a crash.
361: <br>
362: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/025_uipc.patch.sig">
363: A source code patch exists which remedies this problem.</a>
364: <p>
365:
1.24 tj 366: <li id="p026_recvwait">
1.35 bentley 367: <strong>026: RELIABILITY FIX: December 20, 2018</strong>
1.24 tj 368: <i>All architectures</i>
369: <br>
370: While recv(2) with the MSG_WAITALL flag was receiving control
371: messages from a socket, the kernel could panic.
372: <br>
373: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/026_recvwait.patch.sig">
374: A source code patch exists which remedies this problem.</a>
375: <p>
376:
1.25 tj 377: <li id="p027_pcbopts">
1.35 bentley 378: <strong>027: SECURITY FIX: December 22, 2018</strong>
1.25 tj 379: <i>All architectures</i>
380: <br>
381: The setsockopt(2) system call could overflow mbuf cluster kernel
382: memory by 4 bytes.
383: <br>
384: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/027_pcbopts.patch.sig">
385: A source code patch exists which remedies this problem.</a>
386: <p>
387:
1.28 tj 388: <li id="p028_mincore">
1.35 bentley 389: <strong>028: SECURITY FIX: February 5, 2019</strong>
1.28 tj 390: <i>All architectures</i>
391: <br>
392: The mincore() system call can be used to observe memory access patterns
393: of other processes.
394: <br>
395: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/028_mincore.patch.sig">
396: A source code patch exists which remedies this problem.</a>
397: <p>
398:
399: <li id="p029_nfs">
1.35 bentley 400: <strong>029: RELIABILITY FIX: February 5, 2019</strong>
1.28 tj 401: <i>All architectures</i>
402: <br>
403: Missing length checks in the NFS server and client can lead to crashes
404: and other errors.
405: <br>
406: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/029_nfs.patch.sig">
407: A source code patch exists which remedies this problem.</a>
408: <p>
409:
1.29 tj 410: <li id="p030_pf6frag">
1.35 bentley 411: <strong>030: SECURITY FIX: March 1, 2019</strong>
1.29 tj 412: <i>All architectures</i>
413: <br>
414: Fragmented IPv6 packets may be erroneously passed by pf or lead to a crash.
415: <br>
416: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/030_pf6frag.patch.sig">
417: A source code patch exists which remedies this problem.</a>
418: <p>
419:
1.30 tj 420: <li id="p031_pficmp">
1.35 bentley 421: <strong>031: SECURITY FIX: March 22, 2019</strong>
1.30 tj 422: <i>All architectures</i>
423: <br>
424: A state in pf could pass ICMP packets to a destination IP address
425: that did not match the state.
426: <br>
427: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/031_pficmp.patch.sig">
428: A source code patch exists which remedies this problem.</a>
429: <p>
430:
1.31 tj 431: <li id="p032_vmmints">
1.35 bentley 432: <strong>032: SECURITY FIX: March 27, 2019</strong>
1.31 tj 433: <i>amd64 and i386</i>
434: <br>
435: GDT and IDT limits were improperly restored during VMM context switches.
436: <br>
437: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/032_vmmints.patch.sig">
438: A source code patch exists which remedies this problem.</a>
439: <p>
440:
1.34 tj 441: <li id="p033_rip6cksum">
1.35 bentley 442: <strong>033: RELIABILITY FIX: May 3, 2019</strong>
1.34 tj 443: <i>All architectures</i>
444: <br>
445: If a userland program sets the IPv6 checksum offset on a raw socket,
446: an incoming packet could crash the kernel. ospf6d is such a program.
447: <br>
448: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/033_rip6cksum.patch.sig">
449: A source code patch exists which remedies this problem.</a>
450: <p>
451:
1.1 deraadt 452: </ul>
453:
454: <hr>
![[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