Annotation of www/errata70.html, Revision 1.34
1.1 deraadt 1: <!doctype html>
2: <html lang=en id=errata>
3: <meta charset=utf-8>
4:
5: <title>OpenBSD 7.0 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/errata70.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.0 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>,
1.21 deraadt 76: <a href="errata69.html">6.9</a>,
1.31 deraadt 77: <a href="errata71.html">7.1</a>,
1.33 tj 78: <a href="errata72.html">7.2</a>,
1.34 ! 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.0/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.0.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.25 tj 99: <a href="stable.html">-stable branch</a>.
1.1 deraadt 100:
101: <hr>
102:
103: <ul>
104:
1.8 benno 105: <li id="p001_nsd">
1.4 benno 106: <strong>001: RELIABILITY FIX: October 31, 2021</strong>
107: <i>All architectures</i>
108: <br>
109: In certain configurations, nsd(8) can be crashed by a remote attacker.
110: <br>
111: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/001_nsd.patch.sig">
112: A source code patch exists which remedies this problem.</a>
113: <p>
114:
1.8 benno 115: <li id="p002_bpf">
1.4 benno 116: <strong>002: RELIABILITY FIX: October 31, 2021</strong>
117: <i>All architectures</i>
118: <br>
1.6 tj 119: Opening /dev/bpf too often could lead to resource exhaustion.
1.4 benno 120: <br>
121: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/002_bpf.patch.sig">
122: A source code patch exists which remedies this problem.</a>
123: <p>
1.1 deraadt 124:
1.8 benno 125: <li id="p003_uipc">
1.7 benno 126: <strong>003: SECURITY FIX: October 31, 2021</strong>
1.5 benno 127: <i>All architectures</i>
128: <br>
129: The kernel could leak memory when closing unix sockets.
130: <br>
131: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/003_uipc.patch.sig">
132: A source code patch exists which remedies this problem.</a>
133: <p>
134:
1.9 benno 135: <li id="p004_rpki">
136: <strong>004: SECURITY FIX: November 9, 2021</strong>
137: <i>All architectures</i>
138: <br>
139: rpki-client(8) should handle CA misbehaviours as soft-errors.
140: <br>
141: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/004_rpki.patch.sig">
142: A source code patch exists which remedies this problem.</a>
143: <p>
144:
1.10 bluhm 145: <li id="p005_unpcon">
146: <strong>005: RELIABILITY FIX: November 26, 2021</strong>
147: <i>All architectures</i>
148: <br>
149: An unprivileged user could crash the kernel by using UNIX-domain
150: sockets in multiple threads.
151: <br>
152: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/005_unpcon.patch.sig">
153: A source code patch exists which remedies this problem.</a>
154: <p>
155:
156: <li id="p006_x509">
1.11 tj 157: <strong>006: SECURITY FIX: November 26, 2021</strong>
1.10 bluhm 158: <i>All architectures</i>
159: <br>
160: In some situations the X.509 verifier would discard an error on
161: an unverified certificate chain, resulting in an authentication bypass.
162: <br>
163: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/006_x509.patch.sig">
164: A source code patch exists which remedies this problem.</a>
165: <p>
166:
1.12 bluhm 167: <li id="p007_xserver">
168: <strong>007: SECURITY FIX: December 14, 2021</strong>
169: <i>All architectures</i>
170: <br>
171: Multiple input validation failures in the X server request parsing
172: code can lead to out of bounds memory accesses for authorized
173: clients.
174: <br>
175: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/007_xserver.patch.sig">
176: A source code patch exists which remedies this problem.</a>
177: <p>
178:
1.13 bluhm 179: <li id="p008_mrt">
180: <strong>008: SECURITY FIX: December 16, 2021</strong>
181: <i>All architectures</i>
182: <br>
183: If multicast routing is used, kernel memory is leaked to userland.
184: <br>
185: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/008_mrt.patch.sig">
186: A source code patch exists which remedies this problem.</a>
187: <p>
188:
1.14 bluhm 189: <li id="p009_expat">
190: <strong>009: SECURITY FIX: January 19, 2022</strong>
191: <i>All architectures</i>
192: <br>
193: Fix 8 security issues in libexpat, all related to fixed-size integer
194: math (integer overflow and invalid shifts) near memory allocation.
195: <br>
196: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/009_expat.patch.sig">
197: A source code patch exists which remedies this problem.</a>
198: <p>
199:
200: <li id="p010_vmm">
201: <strong>010: RELIABILITY FIX: January 19, 2022</strong>
202: <i>amd64</i>
203: <br>
204: Intel-based vmm(4) hosts may have vm processes die due to host-side
205: state corruption.
206: <br>
207: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/010_vmm.patch.sig">
208: A source code patch exists which remedies this problem.</a>
209: <p>
210:
1.15 bluhm 211: <li id="p011_ppctrap">
212: <strong>011: SECURITY FIX: January 24, 2022</strong>
213: <i>macppc</i>
214: <br>
215: On PowerPC kernel memory is leaked to userland.
216: <br>
217: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/011_ppctrap.patch.sig">
218: A source code patch exists which remedies this problem.</a>
219: <p>
220:
1.16 bluhm 221: <li id="p012_gpuflush">
222: <strong>012: RELIABILITY FIX: February 2, 2022</strong>
223: <i>amd64 i386</i>
224: <br>
225: Userspace controlled code on GPU can access kernel memory on Intel
226: gen 8 and later GPUs.
227: <br>
228: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/012_gpuflush.patch.sig">
229: A source code patch exists which remedies this problem.</a>
230: <p>
231:
232: <li id="p013_expat">
233: <strong>013: SECURITY FIX: February 2, 2022</strong>
234: <i>All architectures</i>
235: <br>
236: Fix two security issues in libexpat related to integer overflow.
237: <br>
238: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/013_expat.patch.sig">
239: A source code patch exists which remedies this problem.</a>
240: <p>
241:
1.17 bluhm 242: <li id="p014_slaacd">
243: <strong>014: SECURITY FIX: February 21, 2022</strong>
244: <i>All architectures</i>
245: <br>
246: More than 7 nameservers in an IPv6 router advertisement could crash slaacd.
247: <br>
248: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/014_slaacd.patch.sig">
249: A source code patch exists which remedies this problem.</a>
250: <p>
251:
1.18 bluhm 252: <li id="p015_expat">
253: <strong>015: SECURITY FIX: February 24, 2022</strong>
254: <i>All architectures</i>
255: <br>
256: Fix five security issues in libexpat related to encoding, stack
257: exhaustion, and integer overflow.
258: <br>
259: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/015_expat.patch.sig">
260: A source code patch exists which remedies this problem.</a>
261: <p>
262:
1.19 bluhm 263: <li id="p016_bignum">
264: <strong>016: SECURITY FIX: March 15, 2022</strong>
265: <i>All architectures</i>
266: <br>
267: A malicious certificate can cause an infinite loop.
268: <br>
269: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/016_bignum.patch.sig">
270: A source code patch exists which remedies this problem.</a>
271: <p>
272:
1.20 bluhm 273: <li id="p017_slaacd">
274: <strong>017: SECURITY FIX: March 22, 2022</strong>
275: <i>All architectures</i>
276: <br>
277: A malicious router advertisement could overflow heap memory in
278: unprivileged slaacd process.
279: <br>
280: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/017_slaacd.patch.sig">
281: A source code patch exists which remedies this problem.</a>
282: <p>
283:
1.22 bluhm 284: <li id="p018_zlib">
285: <strong>018: SECURITY FIX: April 1, 2022</strong>
286: <i>All architectures</i>
287: <br>
288: Memory corruption in zlib can lead to a crash.
289: <br>
290: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/018_zlib.patch.sig">
291: A source code patch exists which remedies this problem.</a>
292: <p>
293:
1.23 bluhm 294: <li id="p019_syszlib">
295: <strong>019: SECURITY FIX: April 5, 2022</strong>
296: <i>All architectures</i>
297: <br>
298: Fix zlib vulnerability in PPP and IPComp compression.
299: <br>
300: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/019_syszlib.patch.sig">
301: A source code patch exists which remedies this problem.</a>
302: <p>
303:
1.24 bluhm 304: <li id="p020_rpki">
305: <strong>020: RELIABILITY FIX: April 11, 2022</strong>
306: <i>All architectures</i>
307: <br>
308: rpki-client(8) handled time zones incorrectly.
309: <br>
310: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/020_rpki.patch.sig">
311: A source code patch exists which remedies this problem.</a>
312: <p>
313:
1.27 bluhm 314: <li id="p021_pppoe">
315: <strong>021: SECURITY FIX: May 16, 2022</strong>
316: <i>All architectures</i>
317: <br>
318: Malicious PPPoE packets could corrupt kernel memory.
319: <br>
320: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/021_pppoe.patch.sig">
321: A source code patch exists which remedies this problem.</a>
322: <p>
323:
1.28 bluhm 324: <li id="p022_xserver">
325: <strong>022: SECURITY FIX: July 24, 2022</strong>
326: <i>All architectures</i>
327: <br>
328: Input validation failures in the X server request parsing code can
329: lead to out of bounds memory accesses for authorized clients.
330: <br>
331: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/022_xserver.patch.sig">
332: A source code patch exists which remedies this problem.</a>
333: <p>
334:
335: <li id="p023_cron">
336: <strong>023: RELIABILITY FIX: July 24, 2022</strong>
337: <i>All architectures</i>
338: <br>
339: cron(8) aborted due to strange poll timevals.
340: <br>
341: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/023_cron.patch.sig">
342: A source code patch exists which remedies this problem.</a>
343: <p>
344:
1.29 bluhm 345: <li id="p024_zlib">
346: <strong>024: SECURITY FIX: August 12, 2022</strong>
347: <i>All architectures</i>
348: <br>
349: A missing length check in zlib could lead to a heap buffer overflow.
350: <br>
351: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/024_zlib.patch.sig">
352: A source code patch exists which remedies this problem.</a>
353: <p>
354:
1.30 bluhm 355: <li id="p025_expat">
356: <strong>025: SECURITY FIX: September 23, 2022</strong>
357: <i>All architectures</i>
358: <br>
359: In libexpat fix heap use-after-free vulnerability CVE-2022-40674.
360: <br>
361: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/025_expat.patch.sig">
362: A source code patch exists which remedies this problem.</a>
363: <p>
364:
1.32 bluhm 365: <li id="p026_smtpd">
366: <strong>026: SECURITY FIX: September 26, 2022</strong>
367: <i>All architectures</i>
368: <br>
369: In smtpd(8), possible use-after-free if TLS handshake fails for
370: outbound connections.
371: <br>
372: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/026_smtpd.patch.sig">
373: A source code patch exists which remedies this problem.</a>
374: <p>
375:
1.1 deraadt 376: </ul>
377:
378: <hr>