Annotation of www/errata28.html, Revision 1.98
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>,
! 73: <a href="errata67.html">6.7</a>.
1.1 deraadt 74: <hr>
75:
1.63 deraadt 76: <p>
1.85 tj 77: Patches for the OpenBSD base system are distributed as unified diffs.
78: Each patch contains usage instructions.
79: All the following patches are also available in one
80: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8.tar.gz">tar.gz file</a>
81: for convenience.
1.1 deraadt 82:
83: <p>
1.85 tj 84: Patches for supported releases are also incorporated into the
1.86 tj 85: <a href="stable.html">-stable branch</a>.
1.63 deraadt 86:
1.1 deraadt 87: <hr>
88:
89: <ul>
1.95 deraadt 90:
91: <li id="zsconsole">
92: <strong>001: RELIABILITY FIX: Nov 10, 2000</strong><br>
93: When running a sparc with a serial console, certain types of interrupts would
94: cause great grief.<br>
95: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/sparc/001_zsconsole.patch">
96: A source code patch exists which remedies this problem.</a>
97: <p>
98:
99: <li id="skey">
100: <strong>002: IMPLEMENTATION FIX: Nov 10, 2000</strong>
1.66 deraadt 101: <i>All architectures</i><br>
1.95 deraadt 102: In ssh(1), skey support for SSH1 protocol was broken. Some people might consider
103: that kind of important.<br>
104: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/002_sshskey.patch">
1.63 deraadt 105: A source code patch exists which remedies this problem.</a>
1.18 millert 106: <p>
1.95 deraadt 107:
108: <li id="qe">
109: <strong>003: RELIABILITY FIX: Nov 17, 2000</strong><br>
110: Configuring a qec+qe causes a NMI panic.<br>
111: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/sparc/003_qe.patch">
1.63 deraadt 112: A source code patch exists which remedies this problem.</a>
1.17 millert 113: <p>
1.95 deraadt 114:
115: <li id="rijndael">
116: <strong>004: RELIABILITY FIX: Nov 17, 2000</strong>
1.66 deraadt 117: <i>All architectures</i><br>
1.95 deraadt 118: First off, AES (Rijndael) encryption and decryption were broken for IPsec
119: and swap encryption.<br>
120: Secondly, the AES code did not work properly on big endian machines.<br>
121: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/004_rijndael.patch">
1.63 deraadt 122: A source code patch exists which remedies this problem.</a>
1.95 deraadt 123: This is the second revision of the patch.
1.14 millert 124: <p>
1.95 deraadt 125:
126: <li id="ftpd">
127: <strong>005: SECURITY FIX: Dec 4, 2000</strong>
1.66 deraadt 128: <i>All architectures</i><br>
1.95 deraadt 129: OpenBSD 2.8's ftpd contains a one-byte overflow in the replydirname() function.<br>
130: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/005_ftpd.patch">
1.63 deraadt 131: A source code patch exists which remedies this problem.</a>
1.95 deraadt 132: You can view the <a href="advisories/ftpd_replydirname.txt">OpenBSD Advisory</a> here.
133: <p>
134:
135: <li id="pcibios">
136: <strong>006: STABILITY FIX: Dec 4, 2000</strong><br>
137: On some machines, a PCIBIOS device driver interrupt allocation bug can cause a
138: kernel hang while probing PCI devices. If you have this symptom, you can disable
139: PCIBIOS as a workaround. To do this,
140: <ul>
141: <li>Enter the User Kernel Configuration by booting with the
142: option "boot -c".
143: <li>Once at the <i>UKC></i> prompt, enter
144: <blockquote><pre>
145: UKC> disable pcibios
146: UKC> quit<!--
147: --></pre></blockquote>
148: <li>See <a href="./faq/faq5.html#5.6">this page</a> after a successful
149: boot for instructions on how to re-write your kernel to disable PCIBIOS
150: permanently.
151: </ul>
1.10 aaron 152: <p>
1.95 deraadt 153:
154: <li id="x_sun3">
155: <strong>007: INSTALL PROBLEM: Dec 4, 2000</strong><br>
156: The X packages
157: <a href="https://ftp.openbsd.org/pub/OpenBSD/2.8/sun3/xshare28.tgz">share28.tgz</a>
158: and
159: <a href="https://ftp.openbsd.org/pub/OpenBSD/2.8/sun3/xfont28.tgz">font28.tgz</a>
160: were not on the CD, and only available via FTP install. These packages can be
161: added post-install by using the following command:
162: <pre>
163: # cd /; tar xvfpz xshare28.tgz
164: # cd /; tar xvfpz xfont28.tgz
165: </pre>
166: <p>
167:
168: <li id="kerberos">
169: <strong>008: SECURITY FIX: Dec 7, 2000</strong>
1.66 deraadt 170: <i>All architectures</i><br>
1.95 deraadt 171: Two problems have recently been discovered in the KerberosIV code.<p>
172: 1. A symlink problem was discovered in the KerberosIV password checking
173: routines /usr/bin/su and /usr/bin/login, which makes it possible for a
174: local user to overwrite any file on the local machine.<p>
175: 2. It is possible to specify environment variables in telnet
176: which will be passed over the to the remote host. This makes it
177: possible to set environment variables on the remote side, including
178: ones that have special meaning on the server. It is not clear at this
179: time what the impact is, but we recommend everyone to upgrade their
180: machines immediately.<p>
181: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/008_kerberos.patch">
1.63 deraadt 182: A source code patch exists which remedies this problem.</a>
1.4 millert 183: <p>
1.95 deraadt 184:
185: <li id="kerberos2">
186: <strong>009: SECURITY FIX: Dec 10, 2000</strong>
1.66 deraadt 187: <i>All architectures</i><br>
1.95 deraadt 188: Another problem exists in the Kerberos libraries.<br>
189: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/009_kerberos2.patch">
1.63 deraadt 190: A source code patch exists which remedies this problem.</a>
1.3 millert 191: <p>
1.95 deraadt 192:
193: <li id="fastroute">
194: <strong>010: RELIABILITY FIX: Dec 11, 2000</strong>
1.66 deraadt 195: <i>All architectures</i><br>
1.95 deraadt 196: A crash could occur during fast routing, if IPSEC was enabled.<br>
197: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/010_fastroute.patch">
1.63 deraadt 198: A source code patch exists which remedies this problem.</a>
1.1 deraadt 199: <p>
1.95 deraadt 200:
201: <li id="hwcrypto">
202: <strong>011: RELIABILITY FIX: Dec 13, 2000</strong>
1.66 deraadt 203: <i>All architectures</i><br>
1.95 deraadt 204: The crypto subsystem could incorrectly fail to run certain software ciphers,
205: if a hardware card existed in the machine.<br>
206: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/011_hwcrypto.patch">
1.63 deraadt 207: A source code patch exists which remedies this problem.</a>
1.1 deraadt 208: <p>
1.95 deraadt 209:
210: <li id="imacdv">
211: <strong>012: INSTALL PROBLEM: Dec 14, 2000</strong><br>
212: The IMac DV+ (and probably some other machines) incorrectly identify their video
213: hardware, but it is possible to work around the problem.<br>
214: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/powerpc/012_imacdv.patch">
1.63 deraadt 215: A source code patch exists which remedies this problem.</a>
1.1 deraadt 216: <p>
1.95 deraadt 217:
218: <li id="procfs">
219: <strong>013: SECURITY FIX: Dec 18, 2000</strong>
1.66 deraadt 220: <i>All architectures</i><br>
1.95 deraadt 221: <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>
222: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/013_procfs.patch">
1.63 deraadt 223: A source code patch exists which remedies this problem.</a>
1.1 deraadt 224: <p>
1.95 deraadt 225:
226: <li id="xlock">
227: <strong>014: SECURITY FIX: Dec 22, 2000</strong>
1.66 deraadt 228: <i>All architectures</i><br>
1.95 deraadt 229: 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>
230: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/014_xlock.patch">
1.63 deraadt 231: A source code patch exists which remedies this problem.</a>
1.1 deraadt 232: <p>
1.95 deraadt 233: 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>
234: and <i>chmod 4755 /usr/X11R6/bin/xlock</i>.
235: <p>
236: <ul>
237: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/i386/xlock">Xlock - i386</a>
238: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/sparc/xlock">Xlock - sparc</a>
239: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/mac68k/xlock">Xlock - mac68k</a>
240: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/powerpc/xlock">Xlock - powerpc</a>
241: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/amiga/xlock">Xlock - amiga</a>
242: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/hp300/xlock">Xlock - hp300</a>
243: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/mvme68k/xlock">Xlock - mvme68k</a>
244: </ul>
1.65 deraadt 245: <p>
1.95 deraadt 246:
247: <li id="pms">
248: <strong>015: STABILITY FIX: Dec 22, 2000</strong><br>
249: Some machines locked up while trying to use the mouse in console mode. This patch solves that problem.<br>
250: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/i386/015_pms.patch">
1.63 deraadt 251: A source code patch exists which remedies this problem.</a>
1.1 deraadt 252: <p>
1.95 deraadt 253:
254: <li id="tl">
255: <strong>016: RELIABILITY FIX: Jan 4, 2001</strong>
1.66 deraadt 256: <i>All architectures</i><br>
1.95 deraadt 257: Allow ThunderLAN cards to share interrupts nicely.<br>
258: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/016_tl.patch">
1.63 deraadt 259: A source code patch exists which remedies this problem.</a>
1.1 deraadt 260: <p>
1.95 deraadt 261:
262: <li id="rnd">
263: <strong>017: SECURITY FIX: Jan 22, 2001</strong>
1.66 deraadt 264: <i>All architectures</i><br>
1.95 deraadt 265: 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>
266: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/017_rnd.patch">
1.63 deraadt 267: A source code patch exists which remedies this problem.</a>
1.1 deraadt 268: <p>
1.95 deraadt 269:
1.70 bentley 270: <li id="named">
1.94 bentley 271: <strong>018: SECURITY FIX: Jan 29, 2001</strong>
1.66 deraadt 272: <i>All architectures</i><br>
1.88 tb 273: Merge <a href="https://man.openbsd.org/OpenBSD-2.8/named.8">named</a>
1.1 deraadt 274: with ISC BIND 4.9.8-REL, which fixes some buffer vulnerabilities (actually it appears
1.13 jsyn 275: that these were already impossible to exploit beforehand).<br>
1.84 tb 276: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/018_named.patch">
1.63 deraadt 277: A source code patch exists which remedies this problem.</a>
1.1 deraadt 278: <p>
1.95 deraadt 279:
280: <li id="lepci">
281: <strong>019: IMPLEMENTATION FIX: Jan 31, 2001</strong>
1.66 deraadt 282: <i>All architectures</i><br>
1.95 deraadt 283: 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>
284: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/019_lepci.patch">
1.63 deraadt 285: A source code patch exists which remedies this problem.</a>
1.1 deraadt 286: <p>
1.95 deraadt 287:
288: <li id="libwrap">
289: <strong>020: IMPLEMENTATION FIX: Feb 15, 2001</strong>
1.66 deraadt 290: <i>All architectures</i><br>
1.95 deraadt 291: 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>
292: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/020_libwrap.patch">
1.63 deraadt 293: A source code patch exists which remedies this problem.</a>
1.1 deraadt 294: <p>
1.95 deraadt 295:
296: <li id="sudo">
297: <strong>021: SECURITY FIX: Feb 22, 2001</strong>
298: <i>All architectures</i><br>
299: There is an exploitable heap corruption bug in
300: <a href="https://man.openbsd.org/OpenBSD-2.8/sudo.8">sudo</a>.
301: <br>
302: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/021_sudo.patch">
1.65 deraadt 303: A source code patch exists which remedies this problem.</a>
304: <p>
1.95 deraadt 305:
306: <li id="userldt">
307: <strong>022: SECURITY FIX: Mar 2, 2001</strong><br>
308: 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.
309: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/i386/022_userltd.patch">
1.63 deraadt 310: A source code patch exists which remedies this problem.</a>
1.1 deraadt 311: <p>
1.95 deraadt 312:
313: <li id="ipsec_ah">
314: <strong>023: SECURITY FIX: Mar 2, 2001</strong>
1.66 deraadt 315: <i>All architectures</i><br>
1.95 deraadt 316: 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>
317: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/023_ip_ah.patch">
1.63 deraadt 318: A source code patch exists which remedies this problem.</a>
1.1 deraadt 319: <p>
1.95 deraadt 320:
321: <li id="readline">
322: <strong>024: SECURITY FIX: Mar 18, 2001</strong>
323: <i>All architectures</i><br>
324: The readline library shipped with OpenBSD allows history files creation
325: with a permissive
326: <a href="https://man.openbsd.org/OpenBSD-2.8/umask.2">umask(2)</a>.
327: This can lead to the leakage of sensitive information in applications
328: that use passwords and the like during user interaction (one such
329: application is mysql).<br>
330: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/024_readline.patch">
1.65 deraadt 331: A source code patch exists which remedies this problem.</a>
332: <p>
1.95 deraadt 333:
334: <li id="glob">
335: <strong>025: SECURITY FIX: Apr 10, 2001</strong>
1.66 deraadt 336: <i>All architectures</i><br>
1.95 deraadt 337: <a href="https://man.openbsd.org/OpenBSD-2.8/glob.3">glob(3)</a> contains multiple buffer overflows. <br>
338: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/025_glob.patch">
1.63 deraadt 339: A source code patch exists which remedies this problem.</a>
1.1 deraadt 340: <p>
1.95 deraadt 341:
342: <li id="glob_limit">
343: <strong>026: SECURITY FIX: Apr 23, 2001</strong>
1.66 deraadt 344: <i>All architectures</i><br>
1.95 deraadt 345: <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>
346: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/026_globlimit.patch">
1.63 deraadt 347: A source code patch exists which remedies this problem.</a>
1.1 deraadt 348: <p>
1.95 deraadt 349:
350: <li id="ipf_frag">
351: <strong>027: SECURITY FIX: Apr 23, 2001</strong>
1.66 deraadt 352: <i>All architectures</i><br>
1.95 deraadt 353: IPF has a serious problem with fragment caching, the bug is triggered if you use the ipf(5) syntax "keep state".<br>
354: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/027_ipf-frag.patch">
1.63 deraadt 355: A source code patch exists which remedies this problem.</a>
1.1 deraadt 356: <p>
1.95 deraadt 357:
358: <li id="sendmail">
359: <strong>028: SECURITY FIX: May 29, 2001</strong>
1.66 deraadt 360: <i>All architectures</i><br>
1.95 deraadt 361: 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
362: context of a signal handler. This leads to potentially serious
363: race conditions. At the moment this is a theoretical attack only
364: and can only be exploited on the local host (if at all).<br>
365: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/028_sendmail.patch">
1.63 deraadt 366: A source code patch exists which remedies this problem.</a>
1.95 deraadt 367: It updates sendmail to version 8.11.4.
1.1 deraadt 368: <p>
1.95 deraadt 369:
370: <li id="fts">
371: <strong>029: SECURITY FIX: May 30, 2001</strong>
1.66 deraadt 372: <i>All architectures</i><br>
1.95 deraadt 373: Programs using the <a href="https://man.openbsd.org/OpenBSD-2.8/fts.3">fts(3)</a>
374: routines (such as rm, find, and most programs that take a <b>-R</b>
375: flag) can be tricked into changing into the wrong directory if the
376: parent dir is changed out from underneath it. This is similar to
377: the old fts bug but happens when popping out of directories, as
378: opposed to descending into them.
379: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/029_fts.patch">
1.65 deraadt 380: A source code patch exists which remedies this problem.</a>
1.95 deraadt 381: This is the second version of the patch.
1.1 deraadt 382: <p>
1.95 deraadt 383:
384: <li id="kernexec">
385: <strong>030: SECURITY FIX: June 15, 2001</strong>
1.66 deraadt 386: <i>All architectures</i><br>
1.95 deraadt 387: 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.
388: <br>
389: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/030_kernexec.patch">
1.65 deraadt 390: A source code patch exists which remedies this problem.</a>
1.1 deraadt 391: <p>
1.95 deraadt 392:
393: <li id="sendmail2">
394: <strong>031: SECURITY FIX: August 21, 2001</strong>
395: <i>All architectures</i><br>
396: A security hole exists in <a href="https://man.openbsd.org/OpenBSD-2.8/sendmail.8">sendmail(8)</a>
397: that may allow an attacker on the local host to gain root privileges by
398: specifying out-of-bounds debug parameters.
399: <br>
400: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/031_sendmail.patch">
1.1 deraadt 401: A source code patch exists which remedies this problem.</a>
402: <p>
1.95 deraadt 403:
404: <li id="lpd">
405: <strong>032: SECURITY FIX: August 29, 2001</strong>
1.66 deraadt 406: <i>All architectures</i><br>
1.95 deraadt 407: A security hole exists in <a href="https://man.openbsd.org/OpenBSD-2.8/lpd.8">lpd(8)</a>
408: that may allow an attacker with line printer access to gain root
409: privileges. A machine must be running lpd to be vulnerable (OpenBSD
410: does not start lpd by default). Only machines with line printer
411: access (ie: listed in either /etc/hosts.lpd or /etc/hosts.equiv)
412: may be used to mount an attack.
413: <br>
414: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/032_lpd.patch">
1.65 deraadt 415: A source code patch exists which remedies this problem.</a>
416: <p>
1.95 deraadt 417:
418: <li id="uucp">
419: <strong>033: SECURITY FIX: September 11, 2001</strong>
420: <i>All architectures</i><br>
421: A security hole exists in <a href="https://man.openbsd.org/OpenBSD-2.8/uuxqt.8">uuxqt(8)</a>
422: that may allow an attacker to run arbitrary commands as user uucp and
423: use this to gain root access.
424: The UUCP execution daemon, uuxqt(8), has a bug in its command line
425: parsing routine may allow arbitrary commands to be run. Because
426: some UUCP commands are run as root (and daemon) from cron it is possible
427: to leverage compromise of the UUCP user to gain root.
428: <br>
429: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.8/common/033_uucp.patch">
1.1 deraadt 430: A source code patch exists which remedies this problem.</a>
431: <p>
1.82 deraadt 432:
1.1 deraadt 433: </ul>
1.61 deraadt 434:
1.71 tedu 435: <hr>