[BACK]Return to errata28.html CVS log [TXT][DIR] Up to [local] / www

Annotation of www/errata28.html, Revision 1.105

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