Annotation of www/errata28.html, Revision 1.100
1.94 bentley 1: <!doctype html>
2: <html lang=en id=errata>
3: <meta charset=utf-8>
4:
1.81 tj 5: <title>OpenBSD 2.8 Errata</title>
1.1 deraadt 6: <meta name="description" content="the OpenBSD CD errata page">
1.79 deraadt 7: <meta name="viewport" content="width=device-width, initial-scale=1">
8: <link rel="stylesheet" type="text/css" href="openbsd.css">
1.83 tb 9: <link rel="canonical" href="https://www.openbsd.org/errata28.html">
1.1 deraadt 10:
1.69 deraadt 11: <!--
12: IMPORTANT REMINDER
13: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
14: -->
15:
1.1 deraadt 16:
1.94 bentley 17: <h2 id=OpenBSD>
1.79 deraadt 18: <a href="index.html">
1.94 bentley 19: <i>Open</i><b>BSD</b></a>
20: 2.8 Errata
1.81 tj 21: </h2>
1.79 deraadt 22: <hr>
1.1 deraadt 23:
1.28 deraadt 24: For errata on a certain release, click below:<br>
1.97 schwarze 25: <a href="errata20.html">2.0</a>,
1.27 deraadt 26: <a href="errata21.html">2.1</a>,
27: <a href="errata22.html">2.2</a>,
28: <a href="errata23.html">2.3</a>,
29: <a href="errata24.html">2.4</a>,
30: <a href="errata25.html">2.5</a>,
31: <a href="errata26.html">2.6</a>,
32: <a href="errata27.html">2.7</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>,
1.31 deraadt 36: <a href="errata32.html">3.2</a>,
1.32 david 37: <a href="errata33.html">3.3</a>,
1.37 david 38: <a href="errata34.html">3.4</a>,
1.38 miod 39: <a href="errata35.html">3.5</a>,
1.39 deraadt 40: <a href="errata36.html">3.6</a>,
1.97 schwarze 41: <br>
1.62 deraadt 42: <a href="errata37.html">3.7</a>,
1.41 deraadt 43: <a href="errata38.html">3.8</a>,
1.42 deraadt 44: <a href="errata39.html">3.9</a>,
1.43 deraadt 45: <a href="errata40.html">4.0</a>,
1.45 merdely 46: <a href="errata41.html">4.1</a>,
1.46 deraadt 47: <a href="errata42.html">4.2</a>,
1.47 deraadt 48: <a href="errata43.html">4.3</a>,
1.49 deraadt 49: <a href="errata44.html">4.4</a>,
1.50 deraadt 50: <a href="errata45.html">4.5</a>,
1.51 deraadt 51: <a href="errata46.html">4.6</a>,
1.53 deraadt 52: <a href="errata47.html">4.7</a>,
1.54 miod 53: <a href="errata48.html">4.8</a>,
1.55 nick 54: <a href="errata49.html">4.9</a>,
1.56 sthen 55: <a href="errata50.html">5.0</a>,
1.57 deraadt 56: <a href="errata51.html">5.1</a>,
1.58 deraadt 57: <a href="errata52.html">5.2</a>,
1.97 schwarze 58: <br>
1.59 deraadt 59: <a href="errata53.html">5.3</a>,
1.60 deraadt 60: <a href="errata54.html">5.4</a>,
1.68 jsg 61: <a href="errata55.html">5.5</a>,
1.72 deraadt 62: <a href="errata56.html">5.6</a>,
1.75 deraadt 63: <a href="errata57.html">5.7</a>,
1.76 deraadt 64: <a href="errata58.html">5.8</a>,
1.82 deraadt 65: <a href="errata59.html">5.9</a>,
1.85 tj 66: <a href="errata60.html">6.0</a>,
1.89 deraadt 67: <a href="errata61.html">6.1</a>,
1.91 deraadt 68: <a href="errata62.html">6.2</a>,
1.92 deraadt 69: <a href="errata63.html">6.3</a>,
1.93 deraadt 70: <a href="errata64.html">6.4</a>,
1.96 deraadt 71: <a href="errata65.html">6.5</a>,
1.98 deraadt 72: <a href="errata66.html">6.6</a>,
1.99 deraadt 73: <a href="errata67.html">6.7</a>,
1.100 ! deraadt 74: <a href="errata68.html">6.8</a>,
! 75: <a href="errata69.html">6.9</a>.
1.1 deraadt 76: <hr>
77:
1.63 deraadt 78: <p>
1.85 tj 79: Patches for the OpenBSD base system are distributed as unified diffs.
80: Each patch contains usage instructions.
81: All the following patches are also available in one
82: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8.tar.gz">tar.gz file</a>
83: for convenience.
1.1 deraadt 84:
85: <p>
1.85 tj 86: Patches for supported releases are also incorporated into the
1.86 tj 87: <a href="stable.html">-stable branch</a>.
1.63 deraadt 88:
1.1 deraadt 89: <hr>
90:
91: <ul>
1.95 deraadt 92:
93: <li id="zsconsole">
94: <strong>001: RELIABILITY FIX: Nov 10, 2000</strong><br>
95: When running a sparc with a serial console, certain types of interrupts would
96: cause great grief.<br>
97: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/sparc/001_zsconsole.patch">
98: A source code patch exists which remedies this problem.</a>
99: <p>
100:
101: <li id="skey">
102: <strong>002: IMPLEMENTATION FIX: Nov 10, 2000</strong>
1.66 deraadt 103: <i>All architectures</i><br>
1.95 deraadt 104: In ssh(1), skey support for SSH1 protocol was broken. Some people might consider
105: that kind of important.<br>
106: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/002_sshskey.patch">
1.63 deraadt 107: A source code patch exists which remedies this problem.</a>
1.18 millert 108: <p>
1.95 deraadt 109:
110: <li id="qe">
111: <strong>003: RELIABILITY FIX: Nov 17, 2000</strong><br>
112: Configuring a qec+qe causes a NMI panic.<br>
113: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/sparc/003_qe.patch">
1.63 deraadt 114: A source code patch exists which remedies this problem.</a>
1.17 millert 115: <p>
1.95 deraadt 116:
117: <li id="rijndael">
118: <strong>004: RELIABILITY FIX: Nov 17, 2000</strong>
1.66 deraadt 119: <i>All architectures</i><br>
1.95 deraadt 120: First off, AES (Rijndael) encryption and decryption were broken for IPsec
121: and swap encryption.<br>
122: Secondly, the AES code did not work properly on big endian machines.<br>
123: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/004_rijndael.patch">
1.63 deraadt 124: A source code patch exists which remedies this problem.</a>
1.95 deraadt 125: This is the second revision of the patch.
1.14 millert 126: <p>
1.95 deraadt 127:
128: <li id="ftpd">
129: <strong>005: SECURITY FIX: Dec 4, 2000</strong>
1.66 deraadt 130: <i>All architectures</i><br>
1.95 deraadt 131: OpenBSD 2.8's ftpd contains a one-byte overflow in the replydirname() function.<br>
132: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/005_ftpd.patch">
1.63 deraadt 133: A source code patch exists which remedies this problem.</a>
1.95 deraadt 134: You can view the <a href="advisories/ftpd_replydirname.txt">OpenBSD Advisory</a> here.
135: <p>
136:
137: <li id="pcibios">
138: <strong>006: STABILITY FIX: Dec 4, 2000</strong><br>
139: On some machines, a PCIBIOS device driver interrupt allocation bug can cause a
140: kernel hang while probing PCI devices. If you have this symptom, you can disable
141: PCIBIOS as a workaround. To do this,
142: <ul>
143: <li>Enter the User Kernel Configuration by booting with the
144: option "boot -c".
145: <li>Once at the <i>UKC></i> prompt, enter
146: <blockquote><pre>
147: UKC> disable pcibios
148: UKC> quit<!--
149: --></pre></blockquote>
150: <li>See <a href="./faq/faq5.html#5.6">this page</a> after a successful
151: boot for instructions on how to re-write your kernel to disable PCIBIOS
152: permanently.
153: </ul>
1.10 aaron 154: <p>
1.95 deraadt 155:
156: <li id="x_sun3">
157: <strong>007: INSTALL PROBLEM: Dec 4, 2000</strong><br>
158: The X packages
159: <a href="https://ftp.openbsd.org/pub/OpenBSD/2.8/sun3/xshare28.tgz">share28.tgz</a>
160: and
161: <a href="https://ftp.openbsd.org/pub/OpenBSD/2.8/sun3/xfont28.tgz">font28.tgz</a>
162: were not on the CD, and only available via FTP install. These packages can be
163: added post-install by using the following command:
164: <pre>
165: # cd /; tar xvfpz xshare28.tgz
166: # cd /; tar xvfpz xfont28.tgz
167: </pre>
168: <p>
169:
170: <li id="kerberos">
171: <strong>008: SECURITY FIX: Dec 7, 2000</strong>
1.66 deraadt 172: <i>All architectures</i><br>
1.95 deraadt 173: Two problems have recently been discovered in the KerberosIV code.<p>
174: 1. A symlink problem was discovered in the KerberosIV password checking
175: routines /usr/bin/su and /usr/bin/login, which makes it possible for a
176: local user to overwrite any file on the local machine.<p>
177: 2. It is possible to specify environment variables in telnet
178: which will be passed over the to the remote host. This makes it
179: possible to set environment variables on the remote side, including
180: ones that have special meaning on the server. It is not clear at this
181: time what the impact is, but we recommend everyone to upgrade their
182: machines immediately.<p>
183: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/008_kerberos.patch">
1.63 deraadt 184: A source code patch exists which remedies this problem.</a>
1.4 millert 185: <p>
1.95 deraadt 186:
187: <li id="kerberos2">
188: <strong>009: SECURITY FIX: Dec 10, 2000</strong>
1.66 deraadt 189: <i>All architectures</i><br>
1.95 deraadt 190: Another problem exists in the Kerberos libraries.<br>
191: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/009_kerberos2.patch">
1.63 deraadt 192: A source code patch exists which remedies this problem.</a>
1.3 millert 193: <p>
1.95 deraadt 194:
195: <li id="fastroute">
196: <strong>010: RELIABILITY FIX: Dec 11, 2000</strong>
1.66 deraadt 197: <i>All architectures</i><br>
1.95 deraadt 198: A crash could occur during fast routing, if IPSEC was enabled.<br>
199: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/010_fastroute.patch">
1.63 deraadt 200: A source code patch exists which remedies this problem.</a>
1.1 deraadt 201: <p>
1.95 deraadt 202:
203: <li id="hwcrypto">
204: <strong>011: RELIABILITY FIX: Dec 13, 2000</strong>
1.66 deraadt 205: <i>All architectures</i><br>
1.95 deraadt 206: The crypto subsystem could incorrectly fail to run certain software ciphers,
207: if a hardware card existed in the machine.<br>
208: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/011_hwcrypto.patch">
1.63 deraadt 209: A source code patch exists which remedies this problem.</a>
1.1 deraadt 210: <p>
1.95 deraadt 211:
212: <li id="imacdv">
213: <strong>012: INSTALL PROBLEM: Dec 14, 2000</strong><br>
214: The IMac DV+ (and probably some other machines) incorrectly identify their video
215: hardware, but it is possible to work around the problem.<br>
216: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/powerpc/012_imacdv.patch">
1.63 deraadt 217: A source code patch exists which remedies this problem.</a>
1.1 deraadt 218: <p>
1.95 deraadt 219:
220: <li id="procfs">
221: <strong>013: SECURITY FIX: Dec 18, 2000</strong>
1.66 deraadt 222: <i>All architectures</i><br>
1.95 deraadt 223: <a href="https://man.openbsd.org/OpenBSD-2.8/mount_procfs.8">Procfs</a> contained numerous overflows, which could lead an intruder to root permissions. Procfs is NOT enabled by default in OpenBSD. <br>
224: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/013_procfs.patch">
1.63 deraadt 225: A source code patch exists which remedies this problem.</a>
1.1 deraadt 226: <p>
1.95 deraadt 227:
228: <li id="xlock">
229: <strong>014: SECURITY FIX: Dec 22, 2000</strong>
1.66 deraadt 230: <i>All architectures</i><br>
1.95 deraadt 231: Improve xlock(1)'s authentication by authenticating via a pipe in an early forked process. No known vulnerability exists, this is just a precautionary patch.<br>
232: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/014_xlock.patch">
1.63 deraadt 233: A source code patch exists which remedies this problem.</a>
1.1 deraadt 234: <p>
1.95 deraadt 235: In addition to a source code patch, new xlock binaries have been created for each architecture listed below. Place these binaries at <i>/usr/X11R6/bin/xlock</i>
236: and <i>chmod 4755 /usr/X11R6/bin/xlock</i>.
237: <p>
238: <ul>
239: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/i386/xlock">Xlock - i386</a>
240: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/sparc/xlock">Xlock - sparc</a>
241: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/mac68k/xlock">Xlock - mac68k</a>
242: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/powerpc/xlock">Xlock - powerpc</a>
243: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/amiga/xlock">Xlock - amiga</a>
244: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/hp300/xlock">Xlock - hp300</a>
245: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/mvme68k/xlock">Xlock - mvme68k</a>
246: </ul>
1.65 deraadt 247: <p>
1.95 deraadt 248:
249: <li id="pms">
250: <strong>015: STABILITY FIX: Dec 22, 2000</strong><br>
251: Some machines locked up while trying to use the mouse in console mode. This patch solves that problem.<br>
252: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/i386/015_pms.patch">
1.63 deraadt 253: A source code patch exists which remedies this problem.</a>
1.1 deraadt 254: <p>
1.95 deraadt 255:
256: <li id="tl">
257: <strong>016: RELIABILITY FIX: Jan 4, 2001</strong>
1.66 deraadt 258: <i>All architectures</i><br>
1.95 deraadt 259: Allow ThunderLAN cards to share interrupts nicely.<br>
260: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/016_tl.patch">
1.63 deraadt 261: A source code patch exists which remedies this problem.</a>
1.1 deraadt 262: <p>
1.95 deraadt 263:
264: <li id="rnd">
265: <strong>017: SECURITY FIX: Jan 22, 2001</strong>
1.66 deraadt 266: <i>All architectures</i><br>
1.95 deraadt 267: The <a href="https://man.openbsd.org/OpenBSD-2.8/random.4">rnd(4)</a> device does not use all of its input when data is written to it.<br>
268: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/017_rnd.patch">
1.63 deraadt 269: A source code patch exists which remedies this problem.</a>
1.1 deraadt 270: <p>
1.95 deraadt 271:
1.70 bentley 272: <li id="named">
1.94 bentley 273: <strong>018: SECURITY FIX: Jan 29, 2001</strong>
1.66 deraadt 274: <i>All architectures</i><br>
1.88 tb 275: Merge <a href="https://man.openbsd.org/OpenBSD-2.8/named.8">named</a>
1.1 deraadt 276: with ISC BIND 4.9.8-REL, which fixes some buffer vulnerabilities (actually it appears
1.13 jsyn 277: that these were already impossible to exploit beforehand).<br>
1.84 tb 278: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/018_named.patch">
1.63 deraadt 279: A source code patch exists which remedies this problem.</a>
1.1 deraadt 280: <p>
1.95 deraadt 281:
282: <li id="lepci">
283: <strong>019: IMPLEMENTATION FIX: Jan 31, 2001</strong>
1.66 deraadt 284: <i>All architectures</i><br>
1.95 deraadt 285: Fix memory allocation in the PCI LANCE driver, <a href="https://man.openbsd.org/OpenBSD-2.8/le.4">le</a>. A side effect of this is that OpenBSD under VMWare now works again.<br>
286: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/019_lepci.patch">
1.63 deraadt 287: A source code patch exists which remedies this problem.</a>
1.1 deraadt 288: <p>
1.95 deraadt 289:
290: <li id="libwrap">
291: <strong>020: IMPLEMENTATION FIX: Feb 15, 2001</strong>
1.66 deraadt 292: <i>All architectures</i><br>
1.95 deraadt 293: Client side ident protocol was broken in libwrap, affecting anything using libwrap including <a href="https://man.openbsd.org/OpenBSD-2.8/tcpd.8">tcpd</a>. The effect of this was that libwrap would never retrieve and log ident values from remote hosts on connections.<br>
294: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/020_libwrap.patch">
1.63 deraadt 295: A source code patch exists which remedies this problem.</a>
1.1 deraadt 296: <p>
1.95 deraadt 297:
298: <li id="sudo">
299: <strong>021: SECURITY FIX: Feb 22, 2001</strong>
300: <i>All architectures</i><br>
301: There is an exploitable heap corruption bug in
302: <a href="https://man.openbsd.org/OpenBSD-2.8/sudo.8">sudo</a>.
303: <br>
304: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/021_sudo.patch">
1.65 deraadt 305: A source code patch exists which remedies this problem.</a>
306: <p>
1.95 deraadt 307:
308: <li id="userldt">
309: <strong>022: SECURITY FIX: Mar 2, 2001</strong><br>
310: The <b>USER_LDT</b> kernel option allows an attacker to gain access to privileged areas of kernel memory. This option is not on by default.
311: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/i386/022_userltd.patch">
1.63 deraadt 312: A source code patch exists which remedies this problem.</a>
1.1 deraadt 313: <p>
1.95 deraadt 314:
315: <li id="ipsec_ah">
316: <strong>023: SECURITY FIX: Mar 2, 2001</strong>
1.66 deraadt 317: <i>All architectures</i><br>
1.95 deraadt 318: Insufficient checks in the IPSEC AH IPv4 option handling code can lead to a buffer overrun leading to a remote DoS. This option is not on by default.<br>
319: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/023_ip_ah.patch">
1.63 deraadt 320: A source code patch exists which remedies this problem.</a>
1.1 deraadt 321: <p>
1.95 deraadt 322:
323: <li id="readline">
324: <strong>024: SECURITY FIX: Mar 18, 2001</strong>
325: <i>All architectures</i><br>
326: The readline library shipped with OpenBSD allows history files creation
327: with a permissive
328: <a href="https://man.openbsd.org/OpenBSD-2.8/umask.2">umask(2)</a>.
329: This can lead to the leakage of sensitive information in applications
330: that use passwords and the like during user interaction (one such
331: application is mysql).<br>
332: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/024_readline.patch">
1.65 deraadt 333: A source code patch exists which remedies this problem.</a>
334: <p>
1.95 deraadt 335:
336: <li id="glob">
337: <strong>025: SECURITY FIX: Apr 10, 2001</strong>
1.66 deraadt 338: <i>All architectures</i><br>
1.95 deraadt 339: <a href="https://man.openbsd.org/OpenBSD-2.8/glob.3">glob(3)</a> contains multiple buffer overflows. <br>
340: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/025_glob.patch">
1.63 deraadt 341: A source code patch exists which remedies this problem.</a>
1.1 deraadt 342: <p>
1.95 deraadt 343:
344: <li id="glob_limit">
345: <strong>026: SECURITY FIX: Apr 23, 2001</strong>
1.66 deraadt 346: <i>All architectures</i><br>
1.95 deraadt 347: <a href="https://man.openbsd.org/OpenBSD-2.8/glob.3">ftpd(8)</a> has a potential DoS related to <a href="https://man.openbsd.org/OpenBSD-2.8/glob.3">glob(3)</a>. This patch introduces a GLOB_LIMIT, eliminating the DoS. You must have <a href="#glob">025_glob.patch</a> installed before installing this patch.<br>
348: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/026_globlimit.patch">
1.63 deraadt 349: A source code patch exists which remedies this problem.</a>
1.1 deraadt 350: <p>
1.95 deraadt 351:
352: <li id="ipf_frag">
353: <strong>027: SECURITY FIX: Apr 23, 2001</strong>
1.66 deraadt 354: <i>All architectures</i><br>
1.95 deraadt 355: IPF has a serious problem with fragment caching, the bug is triggered if you use the ipf(5) syntax "keep state".<br>
356: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/027_ipf-frag.patch">
1.63 deraadt 357: A source code patch exists which remedies this problem.</a>
1.1 deraadt 358: <p>
1.95 deraadt 359:
360: <li id="sendmail">
361: <strong>028: SECURITY FIX: May 29, 2001</strong>
1.66 deraadt 362: <i>All architectures</i><br>
1.95 deraadt 363: The signal handlers in <a href="https://man.openbsd.org/OpenBSD-2.8/sendmail.8">sendmail(8)</a> contain code that is unsafe in the
364: context of a signal handler. This leads to potentially serious
365: race conditions. At the moment this is a theoretical attack only
366: and can only be exploited on the local host (if at all).<br>
367: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/028_sendmail.patch">
1.63 deraadt 368: A source code patch exists which remedies this problem.</a>
1.95 deraadt 369: It updates sendmail to version 8.11.4.
1.1 deraadt 370: <p>
1.95 deraadt 371:
372: <li id="fts">
373: <strong>029: SECURITY FIX: May 30, 2001</strong>
1.66 deraadt 374: <i>All architectures</i><br>
1.95 deraadt 375: Programs using the <a href="https://man.openbsd.org/OpenBSD-2.8/fts.3">fts(3)</a>
376: routines (such as rm, find, and most programs that take a <b>-R</b>
377: flag) can be tricked into changing into the wrong directory if the
378: parent dir is changed out from underneath it. This is similar to
379: the old fts bug but happens when popping out of directories, as
380: opposed to descending into them.
381: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/029_fts.patch">
1.65 deraadt 382: A source code patch exists which remedies this problem.</a>
1.95 deraadt 383: This is the second version of the patch.
1.1 deraadt 384: <p>
1.95 deraadt 385:
386: <li id="kernexec">
387: <strong>030: SECURITY FIX: June 15, 2001</strong>
1.66 deraadt 388: <i>All architectures</i><br>
1.95 deraadt 389: A race condition exists in the kernel <a href="https://man.openbsd.org/OpenBSD-2.8/execve.2">execve(2)</a> implementation that opens a small window of vulnerability for a non-privileged user to <a href="https://man.openbsd.org/OpenBSD-2.8/ptrace.2">ptrace(2)</a> attach to a suid/sgid process.
390: <br>
391: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/030_kernexec.patch">
1.65 deraadt 392: A source code patch exists which remedies this problem.</a>
1.1 deraadt 393: <p>
1.95 deraadt 394:
395: <li id="sendmail2">
396: <strong>031: SECURITY FIX: August 21, 2001</strong>
397: <i>All architectures</i><br>
398: A security hole exists in <a href="https://man.openbsd.org/OpenBSD-2.8/sendmail.8">sendmail(8)</a>
399: that may allow an attacker on the local host to gain root privileges by
400: specifying out-of-bounds debug parameters.
401: <br>
402: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/031_sendmail.patch">
1.1 deraadt 403: A source code patch exists which remedies this problem.</a>
404: <p>
1.95 deraadt 405:
406: <li id="lpd">
407: <strong>032: SECURITY FIX: August 29, 2001</strong>
1.66 deraadt 408: <i>All architectures</i><br>
1.95 deraadt 409: A security hole exists in <a href="https://man.openbsd.org/OpenBSD-2.8/lpd.8">lpd(8)</a>
410: that may allow an attacker with line printer access to gain root
411: privileges. A machine must be running lpd to be vulnerable (OpenBSD
412: does not start lpd by default). Only machines with line printer
413: access (ie: listed in either /etc/hosts.lpd or /etc/hosts.equiv)
414: may be used to mount an attack.
415: <br>
416: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/032_lpd.patch">
1.65 deraadt 417: A source code patch exists which remedies this problem.</a>
418: <p>
1.95 deraadt 419:
420: <li id="uucp">
421: <strong>033: SECURITY FIX: September 11, 2001</strong>
422: <i>All architectures</i><br>
423: A security hole exists in <a href="https://man.openbsd.org/OpenBSD-2.8/uuxqt.8">uuxqt(8)</a>
424: that may allow an attacker to run arbitrary commands as user uucp and
425: use this to gain root access.
426: The UUCP execution daemon, uuxqt(8), has a bug in its command line
427: parsing routine may allow arbitrary commands to be run. Because
428: some UUCP commands are run as root (and daemon) from cron it is possible
429: to leverage compromise of the UUCP user to gain root.
430: <br>
431: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/033_uucp.patch">
1.1 deraadt 432: A source code patch exists which remedies this problem.</a>
433: <p>
1.82 deraadt 434:
1.1 deraadt 435: </ul>
1.61 deraadt 436:
1.71 tedu 437: <hr>