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