Annotation of www/errata71.html, Revision 1.33
1.1 deraadt 1: <!doctype html>
2: <html lang=en id=errata>
3: <meta charset=utf-8>
4:
5: <title>OpenBSD 7.1 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/errata71.html">
10:
11: <!--
12: IMPORTANT REMINDER
13: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
14: -->
15:
16: <h2 id=OpenBSD>
17: <a href="index.html">
18: <i>Open</i><b>BSD</b></a>
19: 7.1 Errata
20: </h2>
21: <hr>
22:
23: For errata on a certain release, click below:<br>
24: <a href="errata20.html">2.0</a>,
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>,
40: <br>
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>,
57: <br>
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>,
68: <a href="errata62.html">6.2</a>,
69: <a href="errata63.html">6.3</a>,
70: <a href="errata64.html">6.4</a>,
71: <a href="errata65.html">6.5</a>,
72: <a href="errata66.html">6.6</a>,
73: <a href="errata67.html">6.7</a>,
74: <br>
75: <a href="errata68.html">6.8</a>,
76: <a href="errata69.html">6.9</a>,
1.13 deraadt 77: <a href="errata70.html">7.0</a>,
1.28 tj 78: <a href="errata72.html">7.2</a>,
1.32 tj 79: <a href="errata73.html">7.3</a>,
1.33 ! tj 80: <a href="errata74.html">7.4</a>,
! 81: <a href="errata75.html">7.5</a>.
1.1 deraadt 82: <hr>
83:
84: <p>
85: Patches for the OpenBSD base system are distributed as unified diffs.
86: Each patch is cryptographically signed with the
87: <a href="https://man.openbsd.org/OpenBSD-7.1/signify.1">signify(1)</a> tool and contains
88: usage instructions.
89: All the following patches are also available in one
90: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1.tar.gz">tar.gz file</a>
91: for convenience.
92:
93: <p>
94: Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
95: utility can be used to apply binary updates on the following architectures:
96: amd64, i386, arm64.
97:
98: <p>
99: Patches for supported releases are also incorporated into the
1.15 tj 100: <a href="stable.html">-stable branch</a>.
1.1 deraadt 101:
102: <hr>
103:
104: <ul>
105:
1.2 bluhm 106: <li id="p001_wifi">
107: <strong>001: RELIABILITY FIX: April 22, 2022</strong>
108: <i>All architectures</i>
109: <br>
110: Many wireless network drivers could not scan access points correctly.
111: <br>
112: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/001_wifi.patch.sig">
1.3 benno 113: A source code patch exists which remedies this problem.</a><br>
1.4 deraadt 114: <b>Notice:</b>
1.6 deraadt 115: Some users will have installed a broken version of the
116: <b>syspatch71-001_wifi.tgz</b> file (which prevents future syspatch files
117: from installing), and must manually perform the following step to force
118: deletion of the old file, and then syspatch forward:<br>
1.4 deraadt 119: <kbd># sed -i /release/d /usr/sbin/syspatch && syspatch -R && syspatch</kbd>
1.7 bluhm 120: <p>
1.3 benno 121:
1.7 bluhm 122: <li id="p002_ipsec">
123: <strong>002: RELIABILITY FIX: May 5, 2022</strong>
124: <i>All architectures</i>
125: <br>
126: When using IPsec, the kernel could crash.
127: <br>
128: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/002_ipsec.patch.sig">
129: A source code patch exists which remedies this problem.</a>
1.1 deraadt 130: <p>
131:
1.8 bluhm 132: <li id="p003_kqueue">
133: <strong>003: RELIABILITY FIX: May 16, 2022</strong>
134: <i>All architectures</i>
135: <br>
136: The kernel could crash due to a race in kqueue.
137: <br>
138: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/003_kqueue.patch.sig">
139: A source code patch exists which remedies this problem.</a>
140: <p>
141:
142: <li id="p004_asn1">
143: <strong>004: RELIABILITY FIX: May 16, 2022</strong>
144: <i>All architectures</i>
145: <br>
146: libcrypto would incorrectly decode certain ASN.1 objects.
147: <br>
148: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/004_asn1.patch.sig">
149: A source code patch exists which remedies this problem.</a>
150: <p>
151:
152: <li id="p005_pppoe">
153: <strong>005: SECURITY FIX: May 16, 2022</strong>
154: <i>All architectures</i>
155: <br>
156: Malicious PPPoE packets could corrupt kernel memory.
157: <br>
158: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/005_pppoe.patch.sig">
159: A source code patch exists which remedies this problem.</a>
160: <p>
161:
1.9 bluhm 162: <li id="p006_xserver">
163: <strong>006: SECURITY FIX: July 24, 2022</strong>
164: <i>All architectures</i>
165: <br>
166: Input validation failures in the X server request parsing code can
167: lead to out of bounds memory accesses for authorized clients.
168: <br>
169: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/006_xserver.patch.sig">
170: A source code patch exists which remedies this problem.</a>
171: <p>
172:
173: <li id="p007_cron">
174: <strong>007: RELIABILITY FIX: July 24, 2022</strong>
175: <i>All architectures</i>
176: <br>
177: cron(8) aborted due to strange poll timevals.
178: <br>
179: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/007_cron.patch.sig">
180: A source code patch exists which remedies this problem.</a>
181: <p>
182:
1.10 bluhm 183: <li id="p008_bgpd">
184: <strong>008: RELIABILITY FIX: August 2, 2022</strong>
185: <i>All architectures</i>
186: <br>
187: bgpd(8) could fail to invalidate nexthops and incorrectly leave them in
188: the FIB or Adj-RIB-Out.
189: <br>
190: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/008_bgpd.patch.sig">
191: A source code patch exists which remedies this problem.</a>
192: <p>
193:
1.11 bluhm 194: <li id="p009_zlib">
195: <strong>009: SECURITY FIX: August 12, 2022</strong>
196: <i>All architectures</i>
197: <br>
198: A missing length check in zlib could lead to a heap buffer overflow.
199: <br>
200: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/009_zlib.patch.sig">
201: A source code patch exists which remedies this problem.</a>
202: <p>
203:
1.12 bluhm 204: <li id="p010_expat">
205: <strong>010: SECURITY FIX: September 23, 2022</strong>
206: <i>All architectures</i>
207: <br>
208: In libexpat fix heap use-after-free vulnerability CVE-2022-40674.
209: <br>
210: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/010_expat.patch.sig">
211: A source code patch exists which remedies this problem.</a>
212: <p>
213:
1.14 bluhm 214: <li id="p011_smtpd">
215: <strong>011: SECURITY FIX: September 26, 2022</strong>
216: <i>All architectures</i>
217: <br>
218: In smtpd(8), possible use-after-free if TLS handshake fails for
219: outbound connections.
220: <br>
221: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/011_smtpd.patch.sig">
222: A source code patch exists which remedies this problem.</a>
223: <p>
224:
1.16 bluhm 225: <li id="p012_expat">
226: <strong>012: SECURITY FIX: November 1, 2022</strong>
227: <i>All architectures</i>
228: <br>
229: In libexpat fix heap use-after-free vulnerability CVE-2022-43680.
230: <br>
231: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/012_expat.patch.sig">
232: A source code patch exists which remedies this problem.</a>
233: <p>
234:
1.17 bluhm 235: <li id="p013_pixman">
236: <strong>013: SECURITY FIX: November 14, 2022</strong>
237: <i>All architectures</i>
238: <br>
239: CVE-2022-44638: An integer overflow in pixman may lead to an out-of-bounds
240: write.
241: <br>
242: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/013_pixman.patch.sig">
243: A source code patch exists which remedies this problem.</a>
244: <p>
245:
1.18 bluhm 246: <li id="p014_unwind">
247: <strong>014: SECURITY FIX: November 26, 2022</strong>
248: <i>All architectures</i>
249: <br>
250: A crafted TCP query from localhost could crash the unwind(8) daemon.
251: <br>
252: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/014_unwind.patch.sig">
253: A source code patch exists which remedies this problem.</a>
254: <p>
255:
1.19 bluhm 256: <li id="p015_xserver">
257: <strong>015: SECURITY FIX: December 14, 2022</strong>
258: <i>All architectures</i>
259: <br>
1.31 jsg 260: In X11 server fix local privileges elevation and remote code
1.19 bluhm 261: execution for ssh X forwarding sessions. This addresses CVE-2022-46340
262: CVE-2022-46341 CVE-2022-46342 CVE-2022-46343 CVE-2022-46344.
263: <br>
264: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/015_xserver.patch.sig">
265: A source code patch exists which remedies this problem.</a>
266: <p>
267:
268: <li id="p016_gpuinv">
269: <strong>016: RELIABILITY FIX: December 14, 2022</strong>
270: <i>amd64 i386</i>
271: <br>
272: TLB entries were not invalidated for all types of engine on
273: 12th generation Intel graphics (Tiger Lake, Rocket Lake, Alder Lake).
274: <br>
275: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/016_gpuinv.patch.sig">
276: A source code patch exists which remedies this problem.</a>
277: <p>
278:
1.20 bluhm 279: <li id="p017_acme">
280: <strong>017: RELIABILITY FIX: December 16, 2022</strong>
281: <i>All architectures</i>
282: <br>
283: Removing a domain can result in an out-of-bounds write in acme-client(8).
284: <br>
285: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/017_acme.patch.sig">
286: A source code patch exists which remedies this problem.</a>
287: <p>
288:
1.21 bluhm 289: <li id="p018_tcp">
290: <strong>018: SECURITY FIX: January 13, 2023</strong>
291: <i>All architectures</i>
292: <br>
293: A TCP packet with destination port 0 that matches a pf divert-to
294: rule could crash the kernel.
295: <br>
296: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/018_tcp.patch.sig">
297: A source code patch exists which remedies this problem.</a>
298: <p>
299:
1.22 bluhm 300: <li id="p019_libxpm">
301: <strong>019: SECURITY FIX: January 17, 2023</strong>
302: <i>All architectures</i>
303: <br>
304: Input validation issues and path validation issues in libXpm can lead
305: to infinite loops, memory corruption or arbitrary command execution.
306: CVE-2022-46285, CVE-2022-44617 and CVE-2022-4883
307: <br>
308: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/019_libxpm.patch.sig">
309: A source code patch exists which remedies this problem.</a>
310: <p>
311:
1.23 bluhm 312: <li id="p020_vmm">
313: <strong>020: SECURITY FIX: January 21, 2023</strong>
1.24 bluhm 314: <i>amd64</i>
1.23 bluhm 315: <br>
316: vmm(4) exposed unsupported cpuid feature flags to guests.
317: <br>
318: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/020_vmm.patch.sig">
319: A source code patch exists which remedies this problem.</a>
320: <p>
321:
322: <li id="p021_vmd">
323: <strong>021: SECURITY FIX: January 21, 2023</strong>
1.24 bluhm 324: <i>amd64</i>
1.23 bluhm 325: <br>
326: vmd(8) exposed unsupported cpuid feature flags to guests.
327: <br>
328: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/021_vmd.patch.sig">
329: A source code patch exists which remedies this problem.</a>
330: <p>
331:
1.25 bluhm 332: <li id="p022_x509">
333: <strong>022: SECURITY FIX: February 7, 2023</strong>
334: <i>All architectures</i>
335: <br>
336: A malicious certificate revocation list or timestamp response token would
337: allow an attacker to read arbitrary memory.
338: <br>
339: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/022_x509.patch.sig">
340: A source code patch exists which remedies this problem.</a>
341: <p>
342:
343: <li id="p023_xserver">
344: <strong>023: SECURITY FIX: February 7, 2023</strong>
345: <i>All architectures</i>
346: <br>
347: CVE-2023-0494: use after free in the Xinput X server extension.
348: <br>
349: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/023_xserver.patch.sig">
350: A source code patch exists which remedies this problem.</a>
351: <p>
352:
353: <li id="p024_smtpd">
354: <strong>024: SECURITY FIX: February 7, 2023</strong>
355: <i>All architectures</i>
356: <br>
357: smtpd(8) could abort due to a connection from a local, scoped ipv6 address.
358: <br>
359: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/024_smtpd.patch.sig">
360: A source code patch exists which remedies this problem.</a>
361: <p>
362:
1.26 bluhm 363: <li id="p025_wscons">
364: <strong>025: RELIABILITY FIX: February 26, 2023</strong>
365: <i>All architectures</i>
366: <br>
367: Missing bounds check in console terminal emulation could cause a kernel
368: crash after receiving specially crafted escape sequences.
369: <br>
370: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/025_wscons.patch.sig">
371: A source code patch exists which remedies this problem.</a>
372: <p>
373:
1.27 bluhm 374: <li id="p026_resolv">
375: <strong>026: SECURITY FIX: March 16, 2023</strong>
376: <i>All architectures</i>
377: <br>
378: Out of bounds accesses in libc resolver.
379: <br>
380: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/026_resolv.patch.sig">
381: A source code patch exists which remedies this problem.</a>
382: <p>
383:
1.29 bluhm 384: <li id="p027_bgpd">
385: <strong>027: RELIABILITY FIX: March 23, 2023</strong>
386: <i>All architectures</i>
387: <br>
388: Incorrect length checks allow an out-of-bounds read in bgpd(8).
389: <br>
390: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/027_bgpd.patch.sig">
391: A source code patch exists which remedies this problem.</a>
392: <p>
393:
1.30 bluhm 394: <li id="p028_xserver">
395: <strong>028: SECURITY FIX: March 29, 2023</strong>
396: <i>All architectures</i>
397: <br>
398: Xserver, CVE-2023-1393: use after free bug in the Composite server extension.
399: <br>
400: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/028_xserver.patch.sig">
401: A source code patch exists which remedies this problem.</a>
402: <p>
403:
1.1 deraadt 404: </ul>
405:
406: <hr>