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