Annotation of www/errata72.html, Revision 1.26
1.1 deraadt 1: <!doctype html>
2: <html lang=en id=errata>
3: <meta charset=utf-8>
4:
5: <title>OpenBSD 7.2 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/errata72.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.2 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>,
77: <a href="errata70.html">7.0</a>,
1.17 tj 78: <a href="errata71.html">7.1</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.2/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.2.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.21 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_x509">
105: <strong>001: SECURITY FIX: October 24, 2022</strong>
106: <i>All architectures</i>
107: <br>
108: Custom verification callbacks could cause the X.509 verifier to fail
109: to store errors resulting from leaf certificate verification.
110: <br>
111: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/001_x509.patch.sig">
112: A source code patch exists which remedies this problem.</a>
113: <p>
114:
115: <li id="p002_asn1">
116: <strong>002: RELIABILITY FIX: October 24, 2022</strong>
117: <i>All architectures</i>
118: <br>
119: Unbreak ASN.1 indefinite length encoding.
120: <br>
121: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/002_asn1.patch.sig">
122: A source code patch exists which remedies this problem.</a>
123: <p>
1.1 deraadt 124:
1.3 bluhm 125: <li id="p003_ukbd">
126: <strong>003: RELIABILITY FIX: October 27, 2022</strong>
127: <i>All architectures</i>
128: <br>
129: Restore operation of Apple-specific Fn-key keyboard sequences.
130: <br>
131: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/003_ukbd.patch.sig">
132: A source code patch exists which remedies this problem.</a>
133: <p>
134:
1.4 bluhm 135: <li id="p004_expat">
136: <strong>004: SECURITY FIX: November 1, 2022</strong>
137: <i>All architectures</i>
138: <br>
139: In libexpat fix heap use-after-free vulnerability CVE-2022-43680.
140: <br>
141: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/004_expat.patch.sig">
142: A source code patch exists which remedies this problem.</a>
143: <p>
144:
1.5 bluhm 145: <li id="p005_pixman">
146: <strong>005: SECURITY FIX: November 14, 2022</strong>
147: <i>All architectures</i>
148: <br>
149: CVE-2022-44638: An integer overflow in pixman may lead to an out-of-bounds
150: write.
151: <br>
152: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/005_pixman.patch.sig">
153: A source code patch exists which remedies this problem.</a>
154: <p>
155:
1.6 bluhm 156: <li id="p006_vmm">
157: <strong>006: RELIABILITY FIX: November 26, 2022</strong>
158: <i>amd64</i>
159: <br>
160: Incorrect reference counting and locking caused a vmm(4) performance
161: regression.
162: <br>
163: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/006_vmm.patch.sig">
164: A source code patch exists which remedies this problem.</a>
165: <p>
166:
167: <li id="p007_unwind">
168: <strong>007: SECURITY FIX: November 26, 2022</strong>
169: <i>All architectures</i>
170: <br>
171: A crafted TCP query from localhost could crash the unwind(8) daemon.
172: <br>
173: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/007_unwind.patch.sig">
174: A source code patch exists which remedies this problem.</a>
175: <p>
176:
177: <li id="p008_pfsync">
178: <strong>008: RELIABILITY FIX: November 26, 2022</strong>
179: <i>All architectures</i>
180: <br>
181: Fix a assertion crash during pfsync state update.
182: <br>
183: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/008_pfsync.patch.sig">
184: A source code patch exists which remedies this problem.</a>
185: <p>
186:
1.7 bluhm 187: <li id="p009_xserver">
188: <strong>009: SECURITY FIX: December 14, 2022</strong>
189: <i>All architectures</i>
190: <br>
1.20 jsg 191: In X11 server fix local privileges elevation and remote code
1.7 bluhm 192: execution for ssh X forwarding sessions. This addresses CVE-2022-46340
193: CVE-2022-46341 CVE-2022-46342 CVE-2022-46343 CVE-2022-46344.
194: <br>
195: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/009_xserver.patch.sig">
196: A source code patch exists which remedies this problem.</a>
197: <p>
198:
199: <li id="p010_vmd">
200: <strong>010: RELIABILITY FIX: December 14, 2022</strong>
201: <i>amd64</i>
202: <br>
203: Fix booting vmd(8) guests from ramdisk with more than 4g of memory.
204: <br>
205: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/010_vmd.patch.sig">
206: A source code patch exists which remedies this problem.</a>
207: <p>
208:
209: <li id="p011_gpuinv">
210: <strong>011: RELIABILITY FIX: December 14, 2022</strong>
211: <i>amd64 i386</i>
212: <br>
213: TLB entries were not invalidated for all types of engine on
214: 12th generation Intel graphics (Tiger Lake, Rocket Lake, Alder Lake).
215: <br>
216: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/011_gpuinv.patch.sig">
217: A source code patch exists which remedies this problem.</a>
218: <p>
219:
1.8 bluhm 220: <li id="p012_acme">
221: <strong>012: RELIABILITY FIX: December 16, 2022</strong>
222: <i>All architectures</i>
223: <br>
224: Removing a domain can result in an out-of-bounds write in acme-client(8).
225: <br>
226: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/012_acme.patch.sig">
227: A source code patch exists which remedies this problem.</a>
228: <p>
229:
1.9 bluhm 230: <li id="p013_tcp">
231: <strong>013: SECURITY FIX: January 13, 2023</strong>
232: <i>All architectures</i>
233: <br>
234: A TCP packet with destination port 0 that matches a pf divert-to
235: rule could crash the kernel.
236: <br>
237: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/013_tcp.patch.sig">
238: A source code patch exists which remedies this problem.</a>
239: <p>
240:
1.10 bluhm 241: <li id="p014_libxpm">
242: <strong>014: SECURITY FIX: January 17, 2023</strong>
243: <i>All architectures</i>
244: <br>
245: Input validation issues and path validation issues in libXpm can lead
246: to infinite loops, memory corruption or arbitrary command execution.
247: CVE-2022-46285, CVE-2022-44617 and CVE-2022-4883
248: <br>
249: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/014_libxpm.patch.sig">
250: A source code patch exists which remedies this problem.</a>
251: <p>
252:
1.11 bluhm 253: <li id="p015_vmm">
254: <strong>015: SECURITY FIX: January 21, 2023</strong>
1.12 bluhm 255: <i>amd64</i>
1.11 bluhm 256: <br>
257: vmm(4) exposed unsupported cpuid feature flags to guests.
258: <br>
259: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/015_vmm.patch.sig">
260: A source code patch exists which remedies this problem.</a>
261: <p>
262:
263: <li id="p016_vmd">
264: <strong>016: SECURITY FIX: January 21, 2023</strong>
1.12 bluhm 265: <i>amd64</i>
1.11 bluhm 266: <br>
267: vmd(8) exposed unsupported cpuid feature flags to guests.
268: <br>
269: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/016_vmd.patch.sig">
270: A source code patch exists which remedies this problem.</a>
271: <p>
272:
1.13 bluhm 273: <li id="p017_sshd">
274: <strong>017: SECURITY FIX: February 2, 2023</strong>
275: <i>All architectures</i>
276: <br>
277: A double-free in the sshd pre-auth unprivileged process (not believed
278: to be exploitable).
279: <br>
280: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/017_sshd.patch.sig">
281: A source code patch exists which remedies this problem.</a>
282: <p>
283:
1.14 bluhm 284: <li id="p018_x509">
285: <strong>018: SECURITY FIX: February 7, 2023</strong>
286: <i>All architectures</i>
287: <br>
288: A malicious certificate revocation list or timestamp response token would
289: allow an attacker to read arbitrary memory.
290: <br>
291: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/018_x509.patch.sig">
292: A source code patch exists which remedies this problem.</a>
293: <p>
294:
295: <li id="p019_xserver">
296: <strong>019: SECURITY FIX: February 7, 2023</strong>
297: <i>All architectures</i>
298: <br>
299: CVE-2023-0494: use after free in the Xinput X server extension.
300: <br>
301: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/019_xserver.patch.sig">
302: A source code patch exists which remedies this problem.</a>
303: <p>
304:
305: <li id="p020_smtpd">
306: <strong>020: SECURITY FIX: February 7, 2023</strong>
307: <i>All architectures</i>
308: <br>
309: smtpd(8) could abort due to a connection from a local, scoped ipv6 address.
310: <br>
311: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/020_smtpd.patch.sig">
312: A source code patch exists which remedies this problem.</a>
313: <p>
314:
1.15 bluhm 315: <li id="p021_wscons">
316: <strong>021: RELIABILITY FIX: February 26, 2023</strong>
317: <i>All architectures</i>
318: <br>
319: Missing bounds check in console terminal emulation could cause a kernel
320: crash after receiving specially crafted escape sequences.
321: <br>
322: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/021_wscons.patch.sig">
323: A source code patch exists which remedies this problem.</a>
324: <p>
325:
1.16 bluhm 326: <li id="p022_resolv">
327: <strong>022: SECURITY FIX: March 16, 2023</strong>
328: <i>All architectures</i>
329: <br>
330: Out of bounds accesses in libc resolver.
331: <br>
332: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/022_resolv.patch.sig">
333: A source code patch exists which remedies this problem.</a>
334: <p>
335:
1.18 bluhm 336: <li id="p023_bgpd">
337: <strong>023: RELIABILITY FIX: March 23, 2023</strong>
338: <i>All architectures</i>
339: <br>
340: Incorrect length checks allow an out-of-bounds read in bgpd(8).
341: <br>
342: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/023_bgpd.patch.sig">
343: A source code patch exists which remedies this problem.</a>
344: <p>
345:
1.19 bluhm 346: <li id="p024_xserver">
347: <strong>024: SECURITY FIX: March 29, 2023</strong>
348: <i>All architectures</i>
349: <br>
350: Xserver, CVE-2023-1393: use after free bug in the Composite server extension.
351: <br>
352: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/024_xserver.patch.sig">
353: A source code patch exists which remedies this problem.</a>
354: <p>
355:
1.22 bluhm 356: <li id="p025_rpki">
357: <strong>025: RELIABILITY FIX: May 26, 2023</strong>
358: <i>All architectures</i>
359: <br>
360: IP address inheritance was handled incorrectly in rpki-client(8).
361: <br>
362: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/025_rpki.patch.sig">
363: A source code patch exists which remedies this problem.</a>
364: <p>
365:
366: <li id="p026_ssl">
367: <strong>026: SECURITY FIX: May 26, 2023</strong>
368: <i>All architectures</i>
369: <br>
370: A double free or use after free could occur after SSL_clear(3).
371: <br>
372: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/026_ssl.patch.sig">
373: A source code patch exists which remedies this problem.</a>
374: <p>
375:
1.23 bluhm 376: <li id="p027_libx11">
377: <strong>027: SECURITY FIX: June 15, 2023</strong>
378: <i>All architectures</i>
379: <br>
380: libX11 CVE-2023-3138 Missing checks in XQueryExtension() return values.
381: <br>
382: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/027_libx11.patch.sig">
383: A source code patch exists which remedies this problem.</a>
384: <p>
385:
1.24 tb 386: <li id="p028_bgpd">
387: <strong>028: RELIABILITY FIX: July 12, 2023</strong>
388: <i>All architectures</i>
389: <br>
390: Incorrect length handling of path attributes in bgpd(8) can lead to a
391: session reset.
392: <br>
393: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/028_bgpd.patch.sig">
394: A source code patch exists which remedies this problem.</a>
395: <p>
396:
397: <li id="p029_httpd">
398: <strong>029: RELIABILITY FIX: July 12, 2023</strong>
399: <i>All architectures</i>
400: <br>
401: A malformed HTTP request can crash httpd(8), if fastcgi is in use.
402: <br>
403: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/029_httpd.patch.sig">
404: A source code patch exists which remedies this problem.</a>
405: <p>
406:
407: <li id="p030_elf">
408: <strong>030: RELIABILITY FIX: July 12, 2023</strong>
409: <i>All architectures</i>
410: <br>
411: Incomplete validation of ELF headers in execve(2).
412: <br>
413: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/030_elf.patch.sig">
414: A source code patch exists which remedies this problem.</a>
415: <p>
416:
417: <li id="p031_bgpd">
418: <strong>031: RELIABILITY FIX: July 12, 2023</strong>
419: <i>All architectures</i>
420: <br>
421: When tracking nexthops over IPv6 multipath routes, or when receiving
422: a NOTIFICATION while reaching an internal limit, bgpd(8) could crash.
423: <br>
424: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/031_bgpd.patch.sig">
425: A source code patch exists which remedies this problem.</a>
426: <p>
427:
1.25 bluhm 428: <li id="p032_ssh_agent">
429: <strong>032: SECURITY FIX: July 19, 2023</strong>
430: <i>All architectures</i>
431: <br>
432: In ssh-agent(1)'s PKCS#11 provider support, remote execution was
433: possible due to controllable access in low-quality libraries. In
434: addition to fixing this, the ability to remotely load PKCS#11
435: libraries is now disabled by default (re-enable with
436: '-Oallow-remote-pkcs11').
437: <br>
438: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/032_ssh_agent.patch.sig">
439: A source code patch exists which remedies this problem.</a>
440: <p>
441:
1.26 ! bluhm 442: <li id="p033_amdcpu">
! 443: <strong>033: SECURITY FIX: July 24, 2023</strong>
! 444: <i>amd64 i386</i>
! 445: <br>
! 446: Workaround for Zenbleed AMD cpu problem. For i386 and amd64 platforms.
! 447: <br>
! 448: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/033_amdcpu.patch.sig">
! 449: A source code patch exists which remedies this problem.</a>
! 450: <p>
! 451:
! 452: <li id="p034_amdfirmware">
! 453: <strong>034: SECURITY FIX: July 24, 2023</strong>
! 454: <i>amd64 i386</i>
! 455: <br>
! 456: Add firmware for AMD cpus, to repair past or potential future bugs.
! 457: For i386 and amd64 platforms.
! 458: <p>
! 459: After this step, "fw_update" and "installboot" must be run.
! 460: <br>
! 461: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/034_amdfirmware.patch.sig">
! 462: A source code patch exists which remedies this problem.</a>
! 463: <p>
! 464:
! 465: <li id="p035_amdcpufirmware">
! 466: <strong>035: SECURITY FIX: July 24, 2023</strong>
! 467: <i>amd64 i386</i>
! 468: <br>
! 469: Install firmware updates for AMD cpus, to repair past or potential future bugs.
! 470: For i386 and amd64 platforms.
! 471: <br>
! 472: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/035_amdcpufirmware.patch.sig">
! 473: A source code patch exists which remedies this problem.</a>
! 474: <p>
! 475:
! 476: <li id="p036_wscons">
! 477: <strong>036: RELIABILITY FIX: July 24, 2023</strong>
! 478: <i>All architectures</i>
! 479: <br>
! 480: Missing bounds check in console terminal emulation could cause a kernel
! 481: crash after receiving specially crafted escape sequences.
! 482: <br>
! 483: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/036_wscons.patch.sig">
! 484: A source code patch exists which remedies this problem.</a>
! 485: <p>
! 486:
1.1 deraadt 487: </ul>
488:
489: <hr>
![[BACK]](/icons/back.gif){kind=icon}
Return to errata72.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www